Digital accessibility
Accessibility audit
Measure the accessibility of your website or app against WCAG 2.1 AA, get a reliable compliance rate and know what to fix first.
Why get an accessibility audit?
The Web Content Accessibility Guidelines (WCAG 2.1, level AA) are the international reference for checking that a digital service can be used by everyone, including with a keyboard, a screen reader or high zoom. EN 301 549, the harmonized European standard, refers to them, which makes them the benchmark for complying with the European Accessibility Act. My method follows RGAA, France’s official accessibility standard, based on WCAG 2.1 AA. Its version 4.1.2 has 106 criteria: my audit checks them one by one and produces the compliance rate you publish in your accessibility statement.
A growing obligation
- In France, since 2005, Article 47 of the law of February 11, 2005 has required public online services to be accessible: websites, intranets, apps and software packages.
- Since 2019, the obligation has also applied to companies with more than €250 million in revenue in France.
- Since June 28, 2025, the European Accessibility Act has applied to e-commerce, banking, transport and media across the EU, whatever the size of the company. Only microenterprises are exempt.
Penalties are now being enforced
In France, Arcom, the digital and media regulator, can impose fines of up to €50,000 per non-compliant service and €25,000 for a missing accessibility statement, multi-year accessibility plan or action plan. France’s consumer protection authority (DGCCRF) can penalize each breach of the European Accessibility Act. In June 2026, the court in Caen ruled that the 71% compliance rate claimed by French retailer Carrefour was not enough: a website “cannot be just a little accessible, it must be fully accessible” (translated from French).
Beyond the risk, an inaccessible journey is an order, a sign-up or an application that never goes through. In France alone, 12 to 15 million people live with a disability.
How the audit works
Scoping
Together, we set the scope and the page sample, the user journeys to test and the test accounts needed.
Audit
Each page is checked against the 106 criteria of RGAA 4.1.2 (WCAG 2.1 AA), with testing tools but mostly by hand: keyboard navigation, screen readers, 200% zoom, code review.
Report
You receive the compliance rate, the complete audit grid and the list of issues, illustrated and ranked by impact and by effort to fix.
Debrief
One hour with your design, development and content teams to go over the priorities and answer questions.
Statement
Your accessibility statement is ready to publish. As options: the multi-year accessibility plan (required in France) and the action plan, then a follow-up audit once the fixes are live.
A representative sample, not the whole site
The RGAA method doesn’t require checking every page, only a sample that represents the whole service. It usually includes 10 to 20 pages:
- the required pages: home, contact, legal notice, accessibility, sitemap, help, login;
- one example of each page template: article, product page, list, search results, dashboard;
- each step of the key journeys: checkout, sign-up, application, payment.
A well-built sample gives a reliable rate that your accessibility statement can safely rely on.
What you receive
- The RGAA 4.1.2 audit grid, criterion by criterion and page by page
- The compliance rate, calculated with the official method
- A prioritized report, with screenshots and recommended fixes
- The accessibility statement, ready to publish
- A one-hour debrief with your teams
How much does an accessibility audit cost?
The price depends mainly on the number of pages in the sample and on content that needs specific testing: checkout flow, videos, interactive charts, downloadable documents. My rates are public, with no hidden fees.
| Sample | Price excl. tax | Working time |
|---|---|---|
| 8 pages | $4,080 | about 5 days |
| 13 pages | $5,680 | about 7 days |
| 22 pages | $8,210 | about 10.5 days |
For your own estimate, itemized line by line, answer a few questions or simply enter your website’s address.
Websites, web apps and mobile apps
- Websites
- Corporate, media and e-commerce websites, with particular attention to checkout flows and forms.
- Web apps
- SaaS products, customer portals, intranets and business tools: data tables, filters, modal dialogs, logged-in journeys.
- Mobile apps
- iOS and Android, tested with VoiceOver and TalkBack. RGAA 5, the next version of the French standard, expected at the end of 2026, will add a dedicated testing method.
An auditor who is also a product designer
For 13 years, I’ve designed software for SaaS companies, large corporations and the public sector. I don’t just deliver a list of issues: my recommendations take into account your design system, your technical constraints and your product priorities. Many issues can be fixed once in a component, and they disappear everywhere.
Latest project delivered: the RGAA audit of TotalEnergies’ Solidarity Portal (Portail Solidarité), in 2026, from the page sample to the presentation to the committee.
Frequently asked questions
Isn’t an automated test enough?
No. Automated tools catch some of the issues, like insufficient contrast or an image without a text alternative. Most accessibility criteria require human judgment: whether a text alternative is relevant, reading order, whether an error message is understandable, use with a keyboard or a screen reader.
How long does an audit take?
Expect about 7 days of work for a 13-page sample. The report is delivered within 3 to 4 weeks, or within 2 weeks with priority turnaround.
What is the compliance rate?
It’s the share of applicable criteria that are met across the sample. Under RGAA, it determines the level you declare: fully compliant at 100%, partially compliant from 50%, non-compliant below that.
Can I publish my accessibility statement after the audit?
Yes. In France, the statement must be based on an audit of the sample. I give it to you ready to publish, with the list of non-accessible content and how users can seek redress.
Will the audit need to be redone with RGAA 5?
Not right away. RGAA 5 builds on version 4.1.2 without contradicting it: what you fix today stays fixed, and existing statements remain valid for 18 months. What’s changing with RGAA 5.
My site isn’t live yet. Can it be audited?
Yes, on a staging environment. It’s actually the best time: fixes cost less before launch.
Ready to measure your accessibility?
A free estimate, with no obligation, in under 2 minutes.
Sources: W3C, WCAG 2.1 · EN 301 549 · Directive (EU) 2019/882 (European Accessibility Act) · in France: law no. 2005-102, art. 47 · decree no. 2019-768 · ordinance no. 2023-859 · Caen Judicial Court, June 4, 2026 · France’s interministerial digital agency (DINUM). For general information only; check with your legal counsel.