The Locked Front Door: Why the EU AI Act Makes Accessibility Non-Negotiable

You’ve constructed a building and it’s passed all the inspections for the last building you built. Planning permission, fire safety, structural certification, all signed off. Then a different inspector arrives, clipboard from a regulation nobody thought to check, and finds the front door doesn't meet the needs of disabled users. The building is compliant and non-compliant at the same time, and the second failure cancels out the first.

A lot of AI systems are about to find themselves in exactly that position, just later than most people currently think.

The deadline moved. The obligation didn’t

A few days ago, the EU's Digital Omnibus on AI entered into force, pushing back the AI Act's high-risk system obligations by 16-months from 2 August 2026 to 2 December 2027. It's tempting to read that as breathing room. It isn't, and here's why.

Buried among those postponed obligations is Article 16(l): providers of high-risk AI systems must meet the accessibility requirements already set out in the Web Accessibility Directive and the European Accessibility Act (EAA). That clause hasn't been softened or removed. It's been rescheduled, along with everything else in the same basket. And critically, the underlying accessibility law it points to was never on the AI Act's timeline in the first place; the EAA has applied since June 2025 regardless of what happens to AI regulation. An AI-powered customer service assistant sitting on an inaccessible retail site doesn't get a grace period just because the AI Act's own clock reset.

The transparency rules land on schedule this Sunday, 2 August 2026: chatbot disclosure, synthetic content labelling, deepfake marking. The accessibility obligation is the one that got the extension. That's the part worth noting, because a 16-month delay is exactly long enough for organisations to quietly stop treating accessibility as part of the AI design brief, then rediscover it in late 2027 as a deadline rather than a decision they already made.

It’s important to also remember that the EAA doesn’t just apply for EU entities, it applies to any business that is serving EU-based users regardless of the location of the entity or the technology infrastructure.

Two Regulations, One Obligation

This isn't a footnote. Hogan Lovells has described Article 16(l)(this will open in a new window) as something closer to a design instruction than a cross-reference: existing EU accessibility law has to shape how a high-risk AI system is built from the outset, not get checked against it after the fact. Where an accessibility barrier stops someone understanding or safely using an AI system's output, that stops being a UX complaint. It becomes a product safety and liability question, particularly now the revised Product Liability Directive treats software and AI systems as products in their own right, capable of being found defective.

In other words: an AI system that a screen-reader user can't operate, or that produces outputs a cognitively disabled user can't interpret, isn't just falling short of best practice. It may be falling short of the law twice over, once under the AI Act and once under the accessibility legislation it defers to.

The EAA already has teeth

Osborne Clarke frames the EAA itself in equally unambiguous terms, describing it as a strict compliance requirement covering hardware and services offered to EU consumers from June 2025 onwards, with obligations running from design through to product information and documentation. Enforcement is proving it. German authorities can impose administrative fines of up to €100,000 per violation under the national implementing law, alongside corrective orders that include withdrawing non-compliant products from the market entirely, and competitors and consumer bodies can bring their own actions through competition law. And on 4 June 2026, a French court ordered Carrefour to make its e-commerce site and app fully accessible within six months, with daily fines of €500 for every day it runs late after that. Carrefour didn’t dispute that it was covered. It argued 71% compliance should be close enough. The court disagreed.

That's the environment any AI system touching EU customers is already operating in, whatever the AI Act's own deadline says.

The Business Case Hiding in Plain Sight

Here's what tends to get lost in the compliance framing: this is also a commercial opportunity that most organisations are leaving on the table.

Across the EU, an estimated 87 million people live with a disability - and the households connected to them, through family, friends and carers, represent a vastly larger pool of purchasing decisions. Globally, disabled consumers and their families are estimated to control around $13 trillion in spending power once family purchasing influence is included. Businesses that get accessibility wrong don't just risk a fine; they risk being invisible to a market segment that is large, loyal, and currently underserved. Disabled consumers and their families are also disproportionately likely to abandon a brand permanently after a single bad accessibility experience; loyalty, once earned, tends to run deep in a market that is used to being overlooked.

Building the Door In, Not Bolting It On

The organisations that will win the AI-implementation battle won't be the ones who treat December 2027 as though it's the starting gun for accessibility. They’ll be the ones designing for inclusion from day one - testing with disabled users, and monitoring continuously as models, prompts and interfaces change, rather than checked cursorily once at launch and forgotten.

The alternative is that building with the beautifully engineered lobby and the door that won't open. Impressive from the outside. Legally exposed, commercially closed, from the inside, and incredibly expensive to fix once it’s been built.

Frequently asked questions

1. Did the AI Act delay change the accessibility rules for AI systems?

No. The Digital Omnibus pushed the AI Act's high-risk obligations back from 2 August 2026 to 2 December 2027. The accessibility requirement moved with that group of obligations. It wasn't softened or dropped.

2. Does the European Accessibility Act still apply to AI systems in the meantime?

Yes, and this is the part most people miss. The EAA has applied since June 2025, on its own timeline, regardless of what happens to the AI Act. An AI system built into a customer-facing product still has to meet it now.

3. What does Article 16(l) actually require?

It requires providers of high-risk AI systems to build in the accessibility standards already set by the Web Accessibility Directive and the EAA, from the design stage, rather than checking for accessibility once the system's already built.