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.
Why late discovery is where projects begin to struggle
The structure is locked in. The glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term are defined. Components have been built, reused, and scaled. At that point, serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service is no longer part of the design glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term.
It becomes a problem to fix.
In my experience, this is where projects start to struggle.
By the time accessibility is being checked, most of the decisions that make it hard have already been made.
Why small fixes expose bigger structural problems
What looks like a small adjustment on the surface quickly exposes deeper issues. A contrast fix is not just a colour change if the entire UI relies on colour to communicate meaning. Adding labels to a form is not straightforward if the form was never structured properly to begin with. Making something keyboard accessible is not 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.
And the harder they are to solve properly.
Key takeaway
Late accessibility fixes rarely stay isolated. They reveal assumptions baked into structure, interaction, and component design.
Why retrofitting works against the product
Because you are no longer working with intent.
You are 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 was not designed to support it. You end up making compromises, layering fixes on top of existing glossaryPatternA reusable solution to a common design problem.Open glossary term, and trying to minimise disruption rather than designing the right solution.
It becomes about what is possible, not what is correct.
Why the product can improve technically without getting better
This is where serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service quietly degrades.
On paper, issues are resolved. Tickets are closed. Audits improve. But the underlying experience often remains fragile. Small inconsistencies creep in. glossaryEdge CaseAn edge case is a rare or extreme scenario that falls outside typical user behaviour.Open glossary term are missed. glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term behave differently depending on how they are accessed.
The product becomes technically improved, but not fundamentally better.
Why late-stage pressure creates the wrong decisions
What makes this more difficult is that the timing often works against you.
Late in a project, there is pressure to launch. Deadlines are set, budgets are tight, and there is 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 is when shortcuts happen.
And those shortcuts rarely hold up.
What changes when accessibility is built in from the start
In contrast, 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 does not rely on a single mode of use.
You are not fixing problems.
You are avoiding them.
This is where the difference becomes clear.
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 is 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.
serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service becomes part of the glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term.
Not something added to it.
Why retrofitting is a false efficiency
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. Fixes take longer, decisions become harder, and the quality of the experience is still limited by what was originally built.
It is a false glossaryEfficiencyEfficiency measures how quickly and easily users can complete tasks once they are familiar with a system.Open glossary term.
serviceAccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service does not fail at the audit stage.
It fails at the point decisions are made without it.
And by the time you are trying to retrofit it, you are already working from the back foot.