Accessibility
Retrofitting accessibility is where projects go wrong
Accessibility problems are usually created much earlier than the audit that exposes them. By the time they are being fixed, the hardest decisions have already been made.
Why late-stage accessibility work becomes expensive and fragile, and why projects move far more smoothly when inclusive design shapes the system from the start.
In short
Why late-stage accessibility work becomes expensive and fragile, and why projects move far more smoothly when inclusive design shapes the system from the start.
Why late discovery is where projects begin to struggle
This is where projects start to struggle. What looks like a small adjustment on the surface quickly exposes deeper issues. A contrast fix isn't just a colour change if the entire UI relies on colour to communicate meaning. Adding labels to a form isn't straightforward if the form was never structured properly to begin with. Making something keyboard accessible isn't a tweak if the glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term glossaryModelA model is a system or representation used to process data and generate outputs, often trained to perform specific tasks.Open glossary term assumes a mouse at every step. The further along the project is, the more expensive those problems become.
The cost curve is not linear either. An issue caught in a wireframe costs a conversation. The same issue caught in a glossaryDesign SystemA design system is a collection of reusable components, guidelines, and standards for building consistent products.Open glossary term component costs a change to every screen using it. Caught after launch, it costs that rebuild plus a remediation plan, a retest, and whatever the delay does to everything queued behind it.
It also tends to surface in the worst possible way: through an external audit, a complaint, or a procurement questionnaire nobody saw coming. By that point serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service has stopped being a design consideration and become a compliance problem with a deadline attached, which is the least useful frame for actually solving it.
By the time accessibility is being checked, most of the decisions that make it hard have already been made.
Why retrofitting works against the product
Because you're no longer working with glossarySearch IntentSearch intent is the underlying goal or purpose behind a user’s query, such as finding information, making a purchase, or navigating to a specific site.Open glossary term. You're working against it. Retrofitting serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service means trying to adapt a glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term that wasn't designed to support it. You end up making compromises, layering fixes on top of existing patterns, and trying to minimise disruption rather than designing the right solution. It becomes about what's possible, not what's correct.
Late in a project, there's pressure to launch. Deadlines are set, budgets are tight, and there's little appetite for reworking core parts of the experience. serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service becomes something to manage within those glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term, rather than something that shapes them. That's when shortcuts happen. And those shortcuts rarely hold up.
There is a second cost that rarely gets counted. Every workaround added at this stage becomes something the team has to maintain and explain. The component now has an exception. The glossaryPatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term now has a glossaryVariantA variant is a version of a design or experience used in testing or experimentation.Open glossary term nobody documented. Six months later the reasoning has gone, and the next person glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term around the exception rather than through it.
Key takeaway
Late accessibility fixes rarely stay isolated. They reveal assumptions baked into structure, interaction, and component design.
What changes when accessibility is built in from the start
When serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service is considered from the beginning, it changes how everything is built. Content is structured properly from the start. Components are designed to work across different inputs. glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term are thought through in a way that doesn't rely on a single mode of use. You're not fixing problems. You're avoiding them.
Projects that glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service in tend to move more smoothly. There's less rework, fewer late-stage surprises, and fewer compromises. Decisions are made with clearer glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term, which leads to more consistent outcomes. Accessibility becomes part of the system, not something added to it.
The irony is that retrofitting often takes more time than doing it properly in the first place. What seems like a quicker approach early on ends up creating more complexity later. serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service doesn't fail at the audit stage. It fails at the point decisions are made without it.
None of this requires an serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service specialist attached to every ticket. It requires three questions asked early enough to matter: can this be operated without a mouse, does this still make sense read aloud in order, and does anything here rely on colour alone to carry meaning. Asked in a design review, they take minutes. Asked after launch, they take a project.
