Accessibility by Default

From Legal Footnote to Design Requirement

Accessibility has spent two decades as the item nobody owned. It sat somewhere between legal, IT, and marketing, usually attended to only after a lawsuit, an audit finding, or a public complaint. That era ended on 28 June 2025, when the European Accessibility Act became enforceable across digital services in the EU — covering banking, e-commerce, e-books, transport ticketing, and telecommunications. For the first time, accessibility carries the same regulatory weight as data protection did after GDPR.

The shift matters because enforcement changes incentives faster than advocacy ever does. Design teams that treated WCAG guidelines as aspirational are now treating them as a release gate. That is not a cultural transformation — it is a compliance deadline. But compliance deadlines, handled well, tend to outlast their original motivation.

The Market Argument Was Always There

The regulatory case for accessibility is new. The commercial case is not. The World Health Organization estimates 1.3 billion people live with significant disability — roughly one in six people globally. That figure includes permanent conditions, but also temporary and situational ones: a broken arm, a noisy environment, a small screen, an ageing parent navigating an app for the first time. Accessible design serves all of them simultaneously.

Accessibility by default is not a parallel product for a minority audience. It is a quality bar that happens to also be a legal one.

Renascence's view is that businesses which continue to frame accessibility as a niche accommodation are miscounting their own addressable market. A checkout flow that fails for keyboard-only users or screen-reader users is not an edge-case bug. It is a structural leak in conversion that has simply never been measured as one.

Why Overlay Widgets Are Losing Ground

For years, the fastest route to a compliance badge was a third-party accessibility overlay — a script bolted onto an existing site promising instant WCAG conformance. Disability advocacy groups and screen-reader users have been consistent and vocal critics of these tools, documenting cases where overlays actively broke navigation or created new barriers. Regulators and litigants have increasingly treated overlays as insufficient evidence of compliance in their own right.

The credible alternative is native accessibility: semantic HTML, proper focus management, sufficient colour contrast, captioning, and keyboard operability built into the design system itself, tested with real assistive technology users rather than automated scanners alone. It is slower to implement and harder to retrofit, which is exactly why doing it early is now a competitive position rather than a cost centre.

What This Means for CX Teams

Accessibility by default reframes a legal obligation as a design discipline. That reframing has three practical consequences. First, accessibility criteria need to sit inside design systems and QA checklists, not in a separate audit that happens after launch. Second, journey mapping needs to explicitly include assistive-technology paths — not as an appendix, but as core journeys tested with the same rigour as the primary flow. Third, procurement and vendor contracts for digital tools should require accessibility conformance up front, because retrofitting a third-party platform after the fact is rarely realistic.

Organisations operating in or selling into the EU no longer have the option of treating this as optional. Everyone else should treat the EAA as an early signal of where accessibility regulation is heading globally, and the 1.3 billion figure as a reminder of the demand that was always there, waiting for the friction to be removed.