Discover the true state
of your product.

An accessibility audit gets a fixed quote before any testing starts. Price follows the unique views, the distinct components and the flows with states behind a login. Total page count barely matters: fifty pages built from six templates is a six-template job, while a booking flow with three payment paths is three flows. The same quote covers the retest and the Accessibility Statement.

An audit of a typical marketing site with up to 15 unique templates takes two to three weeks from kick-off to report. Larger applications with authenticated flows take longer, because we test every state behind the login by hand.

To start an audit we need a staging URL, test accounts for anything behind a login, and half an hour to walk us through the flows that carry your revenue. If a flow ends in a real payment, we also need a sandbox or a card we can use, because a checkout we can't finish is a checkout we can't test. That is the full list.

In practice, both. EN 301 549, the harmonised standard behind the EAA, still points at WCAG 2.1 AA in version 3.2.1, the version the Official Journal of the EU cites. Version 4.1.1, published in September 2026, moves to WCAG 2.2 and takes over once the Official Journal cites it. WCAG 2.2 keeps every 2.1 criterion except 4.1.1 Parsing and adds six at A and AA, so testing against 2.2 answers today's requirement and the next one.

Not on its own. The audit is the evidence: conformance arrives when your team fixes the findings and a retest confirms it, and that is when we prepare the Accessibility Statement you publish. The EAA puts that information in your general terms and conditions (Annex V), and in Poland art. 32 of the 2024 act asks for it in your terms of service or an equivalent document. The report records pass or fail for each WCAG criterion on the pages we tested. We don't issue accessibility certificates.

Then you fix in priority order and document the rest. We rank every finding by its impact on users, so blockers go first. Where meeting a requirement would fundamentally change the service or put a disproportionate burden on your company, the EAA allows an exception, but only with a written assessment against set criteria. In Poland that is art. 21 of the 2024 act, and the documentation has to be kept for five years. An undocumented exception is non-compliance.

Run them, and fix what they find first: it's the cheapest part of the work. Just don't read a clean scan as a pass. When the UK government planted 143 barriers on one page, the best single tool flagged 41% of them, and all the tools together 71%. Focus order that makes no sense, a modal that traps the keyboard, an error message the screen reader stays silent about, a drag-only interaction with no alternative: each takes a person at the keyboard, listening to the screen reader, to find.

Yes, on request, after the retest. The Accessibility Conformance Report is written on the VPAT template and records, criterion by criterion, whether the product conforms. Your customers' procurement teams use it as evidence, and more of them ask for it every year: 83% of organisations in Level Access’s 2026 survey require documented accessibility proof before buying digital products.