If you sell to customers in the EU and employ ten people or more, the law now requires your product to work for people with disabilities. We find what fails, show your engineers the fix, and write the documents buyers and regulators ask for.
button
95.9% of home pages had detectable accessibility failures in February 2026. WebAIM Million
Since 28 June 2025 the Act covers e-commerce, apps, banking, ticketing, travel and most consumer software sold in the EU. The UK has required the same under the Equality Act since 2010.
Fines of up to €100,000 in Germany and €60,000 in Ireland, and a regulator can order a product off the market. Any customer can file a complaint.
EN 301 549, the technical standard behind the Act, gained six new requirements for websites in September 2026. We audit against the current version; an audit against an older one misses what was added since.
None of these are exotic. Illustrative examples, not client findings.
VoiceOver says: button
The Buy button has no name
A blind customer hears one word and stops.
Keyboard: focus lost after Continue
Checkout needs a mouse
The Tab key never reaches the card fields.
Contrast: 2.6 to 1, needs 4.5
Grey text on white
Fails the contrast rule. Older customers give up.
Already selling through an assistant or an MCP server? We audit that channel too.
ChatGPT, Claude and other assistants are starting to buy for customers. They read the labels under your page first, the way a screen reader does, and fall back to the picture only when that fails.
A button with no name stops a blind customer. It sends an agent back to guessing from the screenshot: more steps, more cost, sometimes no purchase. Google's Lighthouse now scores this.
So we test every flow two ways, with assistive technology and with live AI agents, and give you one fix list.
VoiceOver says: button
main
form "Checkout"
textbox "Card number"
textbox "Expiry"
button ""Agent: no name, so it guesses.
Fixed price, agreed on a call before work starts.
Screen readers, keyboard, magnification and two live AI agents over the parts your product is built from, against WCAG 2.2 (web accessibility guidelines) and EN 301 549 (the EU standard). You get a full report, a ranked fix list (importable to Jira), and code change suggestions.
An accessibility statement the Act requires, the conformance report enterprise buyers ask for before they shortlist you, and the US version of that report (a VPAT). Written and signed by an independent certified professional, from what the audit found.
Products change and accessibility can slip. A quarterly re-test, the statement kept current, one call a month.
Procurement questionnaires ask for an accessibility statement. Without one you are off the shortlist, and nobody tells you why.
About one in six people live with a disability. The ones who cannot check out do not complain. They leave.
After a complaint, the deadline is a regulator's. After an audit, it is a sprint you planned.
Buyers and regulators want a report from an independent certified professional, not a scan you ran yourself.
What you sell, where, what it is built with and which customer tasks carry the revenue. We agree the scope on the call and send the fixed price in the proposal after it.
Our harness captures every page and step in scope, runs its checks, drives each flow with two live AI agents, and walks it with the NVDA and VoiceOver screen readers. Then a named person confirms every finding by hand on a real screen reader.
The report leads with what stops a customer, each finding with a screenshot, the cause and a draft fix in your framework. Your engineer imports it into your tracker, we take your team through the worst of it at the readout, and we retest the fixes within ninety days.
Not answered here? Book a call and ask.
Directly, only if you sell to consumers. Indirectly, yes: public bodies in the EU must buy accessible software, and enterprise buyers ask for proof before they shortlist a supplier.
For a website or app, yes, while you have fewer than ten staff and under €2 million turnover. The duty arrives the day you cross either line, and your enterprise customers will ask before the law does.
A public page that says which standard you meet, what does not yet comply, and how a customer can complain. The Act requires one. We write it from what the audit confirmed.
Two things wearing four names. The accessibility statement is the public page EU law requires: what you meet, what you do not yet, how to complain. The conformance report is the evidence behind it, one line per requirement. A VPAT is the US template for that report; filled in, it is called an ACR, and its EU edition covers EN 301 549.
Selling in the EU: the statement and the report. Selling to US enterprise or government: add the VPAT. All of them come from one audit.
Probably not in full. The standard changes, most recently in September 2026, and your product has changed since. We re-test against the current version and tell you what moved.
They should, and we show them how. A scanner catches the mechanical faults. It cannot tell you whether a blind customer can finish checkout, and a report you wrote about yourself carries little weight with a buyer or a regulator.
The automated layer is axe-core, Lighthouse and our own scripted checks, run from Playwright against every page and step we capture, with a vision model reading every screenshot. The agent layer is two live AI agents, one on Claude and one on an OpenAI model, driving your key flows five times each.
The human layer is a named person going through each flow with NVDA on Windows, VoiceOver on the Mac and the iPhone, TalkBack as a spot check, the keyboard alone, and the screen magnified. Nothing reaches the report from the automated layer until that person has confirmed it on your build.
Both are fixed on the first call, based on how many distinct parts your product is built from and how many customer journeys matter. No hourly billing. The date we agree is the date we deliver.
Without a portal. If you have had audit findings pushed into Jira through a vendor platform and its connector, you know how that goes: another login, an integration to set up, and issues that arrive thin, without the evidence.
We hand you the findings as a folder and a small command-line tool. Your engineer runs it with their own Jira token and gets one issue per finding, with the annotated screenshot, the clip and a plain-text version attached, labelled by component and owner. The tool talks to your Jira site and nothing else, nobody at Operable gets access, and no Jira admin is needed. The same findings also come as a spreadsheet and as deep links from the report, and if you use another tracker, tell us which one.
Tell us what you sell and where. We reply within two working days.
Book a thirty-minute call (opens in a new tab)Or email [email protected].