Web development
RGAA, WCAG, EAA in plain English: the executive guide to digital accessibility
Accessibility · RGAA · WCAG · EAA
Since June 28, 2025, digital accessibility is no longer only a design-quality topic. For many services in the European Union, it is now a compliance, evidence and business-risk topic.
- EAA The European legal trigger that moves accessibility onto the executive agenda.
- RGAA The French method used to audit, declare and document accessibility.
- WCAG The international technical standard behind most accessibility requirements.
- 95.9% Home pages with detectable WCAG failures in the WebAIM Million 2026 study.
References checked on June 28, 2026. This guide explains what leaders need to decide, audit and prove, without hiding behind jargon.
Short answer
RGAA, WCAG and EAA do not mean the same thing. Together, they change how a digital service is governed.
Accessibility has often been treated as a technical concern, a public-sector concern, or a late-stage checklist. That reading is now too narrow. The European Accessibility Act, or EAA, applies from June 28, 2025 to many products placed on the EU market and services provided in the EU. In France, it also connects to concrete enforcement powers and financial sanctions.
The executive question is no longer only: "Is our website comfortable to use?" The sharper question is: "Is the digital service accessible, provable and maintainable?" A polished interface, a good automated score or a tidy design system can still hide a blocked checkout, a form that cannot be corrected, a modal that traps keyboard users, or a declaration that does not match the real scope.
To steer the topic correctly, separate three layers. EAA creates legal obligations for specific product and service categories. WCAG defines the technical accessibility criteria. RGAA gives France a practical method for testing, reporting and publishing accessibility evidence.
WCAG explains the rules. RGAA helps audit them. EAA turns accessibility into a legal and business risk.
Plain translation
The difference between RGAA, WCAG, EAA and EN 301 549 fits in one table.
The common mistake is to mix a technical standard, an audit method and a legal obligation. A leader does not need to memorize every criterion. They need to know which layer answers which question, then ask for the right evidence.
| Layer | Role | What it changes | Executive question |
|---|---|---|---|
| WCAG | The international reference for making web content accessible. | It defines testable criteria around perception, keyboard use, understanding and technical robustness. | Which level are we targeting, and which pages were actually tested? |
| RGAA | The French accessibility framework, with criteria, tests and methodology. | It translates WCAG principles into a concrete audit, correction and declaration process in France. | Do we have a dated audit, a clear scope and a credible statement? |
| EAA | The European Accessibility Act, implemented through national rules. | It makes accessibility mandatory for defined economic categories, with national controls and sanctions. | Is our product or service covered, and can we demonstrate compliance? |
| EN 301 549 | The European accessibility standard for ICT products and services. | It often acts as the bridge between European requirements and technical WCAG checks. | Which operational standard should our scope use as proof? |
Market signal
The WebAIM number leaders should not ignore: 95.9%.
In the 2026 WebAIM Million report, 95.9% of tested home pages had detectable WCAG failures. That number does not mean every site is legally non-compliant. It means the web still produces accessibility defects at industrial scale, including on pages that look modern, expensive and professionally designed.
The most common failures are not exotic edge cases. They are basic production issues: insufficient contrast, home pages with at least one image missing alternative text, missing form labels and empty links. These are exactly the kinds of defects that appear when accessibility is added at the end instead of designed into content, components and QA.
| Failure type | Share of home pages | Business reading |
|---|---|---|
| Low contrast text | 83.9% | Users may miss key information, calls to action or form states. |
| Home pages with missing image alternative text | 53.1% | At least one image can become invisible or meaningless to assistive technologies and AI extraction. |
| Missing form labels | 51.0% | Leads, checkouts, registrations and support flows become harder to complete. |
| Empty links | 46.3% | Navigation becomes ambiguous, especially for screen-reader and keyboard users. |
EAA scope
The EAA does not cover every website. It covers services and products where the website may be part of the service.
This nuance matters. A brochure website is not automatically covered just because it exists. But a digital journey used to buy, pay, book, manage an account, access a transport service, subscribe to a banking service, read an ebook or use an electronic communication service may sit inside an EAA-covered perimeter.
The right question is not "Do we have a website?" It is "Which covered product or service does this digital interface enable?" For executives, that means the first task is scope qualification: list the services, digital journeys, customer actions, documents, mobile screens and third-party steps that form the actual user experience.
One exemption matters for smaller service providers. Microenterprises, meaning businesses with fewer than 10 people and annual turnover or annual balance sheet total not exceeding EUR 2 million, are not subject to the same EAA obligations for covered services. This should be checked before launching a heavy audit, especially for a small business that is growing or changing its model.
| If the interface lets users… | Why it matters | Decision to make |
|---|---|---|
| Buy products or services online | E-commerce is one of the visible EAA triggers. | Audit the full purchase path, not just the home page. |
| Open, manage or pay through an account | Forms, authentication, payment and customer-space journeys carry high user impact. | Include errors, confirmations, PDF documents and account states. |
| Book transport or access travel information | Transport services are part of the European accessibility perimeter. | Check booking, timetable, ticketing and disruption information. |
| Deliver ebooks, media or telecom-related services | Several digital content and communication services are covered. | Check the service interface, content formats and support path together. |
Legal pressure in France
In France, executives should understand two enforcement tracks that can coexist.
If your service is provided in France or your organization falls under French accessibility obligations, the topic is not abstract. The EAA implementation sits alongside the older French digital accessibility regime under Article 47 of the 2005 disability law. The authorities, triggers and amounts are not identical, but the practical message is simple: weak accessibility evidence can become an enforcement issue.
For the EAA track, Article R451-4 of the French Consumer Code refers to a fifth-class fine when covered products or services placed on the market or provided after June 28, 2025 fail to meet accessibility requirements. Under French criminal-code amounts, a fifth-class fine is EUR 1,500 for a natural person and EUR 7,500 for a legal entity; when repeat-offence rules apply, those amounts can rise to EUR 3,000 and EUR 15,000. The Consumer Code can also support a daily penalty of up to EUR 3,000 per day, capped at EUR 300,000.
For the Article 47 / RGAA track, ARCOM can sanction covered organizations up to EUR 50,000 per online service, and up to EUR 25,000 for failure to publish the required accessibility declaration. A new sanction can be pronounced if the same breach still exists after six months.
| Track | Authority | Financial exposure | What leaders should ask for |
|---|---|---|---|
| EAA / Consumer Code | DGCCRF | Fifth-class fine: up to EUR 7,500 for a legal entity, EUR 15,000 when repeat-offence rules apply. Daily penalty: up to EUR 3,000/day, capped at EUR 300,000. | A mapped EAA scope, service evidence, correction plan and traceable decisions. |
| Article 47 / RGAA | ARCOM | Up to EUR 50,000 per online service, EUR 25,000 for missing declaration, with renewed sanction possible if the same breach persists six months. | A dated declaration, audit scope, tested sample, RGAA rate and remediation roadmap. |
The fine is not the only risk. The expensive part is usually emergency remediation, public exposure, procurement friction and repeated defects in the design system.
Seven-question scope test
Before debating criteria, qualify the perimeter.
This test is not a legal opinion. It is an executive triage tool. If several answers are "yes" or "unknown", the topic should move from the backlog to a scoped compliance and product-quality review.
| Question | Why it matters | Next step |
|---|---|---|
| Can users buy, book, pay, subscribe or manage an account? | These journeys often carry the legal and commercial risk. | Map the whole journey, including errors and confirmation screens. |
| Does the service target EU customers or users? | The EAA is an EU-market topic, not just an internal design preference. | Clarify countries, entities and contractual responsibilities. |
| Are PDFs, emails, customer spaces or mobile screens part of the service? | Accessibility risk rarely stops at the public website. | Include the real artefacts users need to complete the task. |
| Can the main journey be completed with a keyboard only? | Keyboard access reveals blocking issues that scores often miss. | Test menu, forms, modals, checkout and account flows. |
| Do forms expose labels, instructions and error messages properly? | Forms are where accessibility defects become lost leads or failed service. | Test empty, invalid and corrected submissions. |
| Is there a dated accessibility statement? | A statement without scope and evidence can become a liability. | Align the statement with the audit, limits and action plan. |
| Can the team prove how defects are prevented after release? | Compliance decays when components, content and QA are unmanaged. | Add accessibility checks to design, development and publishing workflows. |
No jargon
Accessibility means four simple things: perceive, operate, understand, withstand change.
WCAG is often summarized through four principles: perceivable, operable, understandable and robust. The plain-English version is easier to use in a steering meeting.
| Principle | Plain meaning | Typical proof |
|---|---|---|
| Perceivable | Users can see, hear or otherwise receive the information. | Contrast, alternatives, captions, structure and meaningful content order. |
| Operable | Users can navigate and complete actions without a mouse. | Keyboard journey, visible focus, reachable controls and no traps. |
| Understandable | Users know what is happening and how to correct mistakes. | Clear labels, instructions, error messages and predictable behavior. |
| Robust | The interface still works across browsers, assistive technologies and future updates. | Semantic HTML, valid ARIA, stable components and regression testing. |
Defects that matter
Ten accessibility defects create most of the business risk.
Leaders do not need to start with a catalogue of every criterion. They need to know where accessibility breaks the service. In practice, the same families of defects keep returning.
- Low contrast that makes important text, buttons, errors or disabled states hard to read.
- Missing text alternatives for meaningful images, icons, charts or controls.
- Forms without labels, instructions, grouped options or announced errors.
- Keyboard traps in menus, carousels, pop-ins, chat widgets or cookie banners.
- Invisible focus that prevents users from knowing where they are.
- Ambiguous links and buttons such as repeated "read more" labels with no context.
- Incorrect headings that make pages harder to scan and navigate.
- ARIA used as decoration instead of matching real component behavior.
- PDFs and documents forgotten even though they are required to complete the service.
- Accessibility absent from releases, so defects return after each redesign or content update.
Overlay trap
An accessibility plugin cannot replace accessible design, code and content.
Accessibility overlays and widgets can add display options. They cannot reliably fix the underlying service: semantic structure, form logic, JavaScript behavior, keyboard order, error messaging, documents, procurement obligations or editorial governance. They also cannot write your evidence.
A serious accessibility program works closer to the source: design tokens, components, HTML, ARIA only when necessary, content rules, QA tests, procurement requirements and release checks. The goal is not to add an accessibility button. The goal is to make the actual journey work.
30 / 60 / 90 days
A practical roadmap: scope first, then fix, then prove.
| Timing | Objective | Actions | Evidence |
|---|---|---|---|
| Days 1-30 | Qualify the perimeter and identify blocking journeys. | Map covered services, key pages, customer journeys, documents, tools and third parties. | Scope note, risk map, initial defects, decision log. |
| Days 31-60 | Correct the high-risk defects and shared components. | Fix forms, navigation, focus, contrast, labels, headings, components and document templates. | Tickets, before/after captures, component rules, manual test notes. |
| Days 61-90 | Publish credible proof and prevent regression. | Finalize audit sample, statement, remediation plan, release checks and ownership. | Accessibility statement, audit report, backlog, QA checklist, review date. |
Evidence
A credible accessibility file is not a score. It is a set of dated, scoped proofs.
| Proof | Why it matters | What weak proof looks like |
|---|---|---|
| Scope | Shows what was included and what was excluded. | "The website was checked" with no pages, journeys or documents named. |
| Reference standard | Clarifies whether the audit uses RGAA, WCAG, EN 301 549 or another requirement. | A generic accessibility badge with no methodology. |
| Manual journey tests | Detects keyboard, focus, screen-reader and form failures that tools miss. | Only a Lighthouse or automated-tool screenshot. |
| Defect backlog | Turns findings into accountable remediation. | A PDF audit with no owner, priority or due date. |
| Statement and review date | Makes the current status visible and time-bound. | An old statement that overclaims full compliance. |
WCAG 2.1 or 2.2?
For France today, document WCAG 2.1 AA via RGAA / EN 301 549. Use WCAG 2.2 as anticipation.
This is where many articles stay vague. The practical answer is clearer: the current French regulatory base uses RGAA 4.1.2 and EN 301 549, aligned operationally with WCAG 2.1 level AA. Targeting WCAG 2.2 is still smart, because it reduces future debt and improves real usability, but the compliance file must state the reference actually required for the audited perimeter.
In other words: do not sell "WCAG 2.2 compliant" as a shortcut if the statement, audit method and legal perimeter require another frame. Use 2.2 to raise quality; use the applicable standard to prove compliance.
Board-level questions
Twelve questions an executive committee can ask tomorrow.
- Which of our products or services may be covered by the EAA?
- Which countries, entities and contracts are involved?
- Which digital journeys create the highest user and legal exposure?
- Can the main journey be completed with a keyboard only?
- Do our forms have labels, instructions and accessible errors?
- Which PDFs, emails or customer documents are part of the service?
- What standard and audit method are we using?
- When was the last representative manual test performed?
- What does our accessibility statement claim, and can we prove it?
- Which defects are in the backlog, with owners and deadlines?
- How do we prevent accessibility regressions after release?
- Who owns accessibility across legal, product, design, content and engineering?
Reading path
What to read next if you want to turn the topic into action.
Start with the public Edikka accessibility page to see how an accessibility file can expose method, scope and limits. Then read the analysis on Lighthouse 100 and accessibility to understand why automated scores are useful but insufficient. If your service may be covered by EAA, ask for a perimeter review before launching isolated fixes.
Sources checked
The figures and legal references behind this guide.
This article uses official or primary references where available: the European Commission page on the European Accessibility Act, the official French RGAA portal, the W3C WCAG documentation, the WebAIM Million 2026 report, French Consumer Code articles R451-4 and L521-1, French Criminal Code articles 131-13 and 131-41, and Article 47 of France’s 2005 disability law.
Conclusion
Accessibility is no longer a side note. It is service quality with legal consequences.
The organizations that handle accessibility well will not be those that buy the most visible widget or chase the prettiest automated score. They will be the ones that qualify their scope, fix the journeys that matter, document their decisions and keep accessibility alive inside design, content, engineering and governance.
RGAA, WCAG and EAA can sound technical. The executive lesson is simple: if users depend on a digital service, that service must work, and the organization must be able to prove it.
Edikka operating view
Three levers make accessibility credible.
Map the legal and service scope before the audit
Accessibility risk sits in the real service: checkout, account, booking, payment, documents, mobile states and third-party steps. A serious program starts by mapping the journeys that create value or obligation, then deciding what must be tested and proven first.
Fix the system, not isolated symptoms
One missing label can be fixed in minutes. A design system that repeats the same form, focus or contrast defect across every product is much more expensive. Components, editorial rules and keyboard QA need to become production habits.
Prove, publish and maintain
Accessibility is defended with traces: scope, standard, manual tests, tickets, arbitration, limits and review date. The aim is not to claim perfection once; it is to show a reliable trajectory and prevent the same failures from coming back.
Go further on this topic
Additional answers to clarify the key points covered in this article.
