Accessibility Isn't a Legal Chore — It's the Same Structure Machines Read

Since the European Accessibility Act began applying in June 2025, a lot of businesses have filed website accessibility under "legal chore." Reports from the first year suggest enforcement has mostly been complaint-driven and corrective-first, a notice and a deadline rather than headline fines, which has let many teams quietly decide it can wait. The common shortcut is an overlay plugin: add a widget, tick a box, move on. It's an understandable instinct. It also treats a build-quality problem as a paperwork problem.

Most accessibility failures are structure failures

Look at what actually goes wrong on a typical site. Headings chosen for how big they look rather than what they mean. Buttons that are really clickable divs with no label. Images with no text alternative. Text that's too faint against its background. Menus that can't be reached with a keyboard. Not one of these is a content problem or a legal-language problem. They're decisions made while the page was built, usually for speed or looks, that nobody checked against a person who isn't using a mouse and a large screen.

An overlay sits on top of that structure and tries to paper over it. It can't change what the page is underneath, which is why practitioners have warned for years against treating one as compliance, and why at least one vendor has already faced regulatory action over claims that its tool made sites conformant.

It's cheapest at the start, and the bill always arrives

The same logic runs through the hidden cost of fast-built software. Contrast, focus states, motion, form labels, heading order: these are design and build decisions that cost almost nothing when made on day one and a surprising amount when retrofitted across a finished site. It's the same pattern as a site that looks finished and still fails Core Web Vitals: the visible surface can pass every review while the structure underneath quietly doesn't.

The structure doesn't only serve people

Here's the part that rarely makes the compliance conversation. A page with a logical heading order, labelled controls, real links, and text alternatives is easier for a screen reader to read, and also easier for anything else that has to parse it. Search crawlers and AI systems rely on that same semantic structure to work out what a page is and what it says, the foundation behind getting cited by AI in the first place. Building accessibly isn't a trade against SEO or performance. It's mostly the same work.

A five-minute test

Put the mouse aside and tab through your homepage: can you reach everything, see where you are, and operate it? Zoom the browser to 200%: does the layout survive? Turn on a screen reader for a few minutes: does the page make sense in order? Automated checkers are worth running, but they catch only a portion of real problems. These three checks will usually find the rest.

This is a Build post — the third of our four stages: Define, Express, Build, Grow. If your site passes every visual review but nobody has ever tried it without a mouse, /software is where that gets found before it gets expensive.