When launching digital services in France, you face a compliance decision that impacts audit scope, documentation, and legal exposure. The question isn't whether to pursue accessibility conformance, but which standard framework to implement.
This guide helps you decide whether WCAG 2.2 AA conformance is sufficient or if you must implement the stricter RGAA 4.1.2 framework.
The Decision You're Facing
Your team must choose between two paths:
Path A: Implement WCAG 2.2 AA as your accessibility baseline
Path B: Implement RGAA 4.1.2 with its 106 precise tests and mandatory French-language documentation
Choosing incorrectly risks regulatory penalties up to €20,000 per digital service annually, disqualification from public procurement opportunities, and public listing as non-compliant by French authorities.
Key Factors That Affect Your Choice
Four factors determine your path:
Legal jurisdiction: Does French law apply to your digital services?
Entity type: Are you a public body, large private organization, or vendor to French public entities?
Revenue threshold: Does your organization exceed €250 million in average annual turnover?
Service scope: Do you operate public services of general interest in France?
Your answers dictate whether RGAA compliance is mandatory or if WCAG 2.2 AA provides enough coverage.
Path A: WCAG 2.2 AA Is Sufficient
Choose this path if:
- You're a private organization with less than €250 million average annual turnover
- Your digital services don't operate in France
- You don't provide products or services to French public entities
- Your tools are purely internal (intranet systems not accessible to the public)
- You're not subject to European Accessibility Act requirements in France
What you implement:
Conduct conformance testing against WCAG 2.2 Level AA success criteria. Deliverables include an Accessibility Conformance Report documenting test results, a voluntary accessibility statement, and remediation of identified barriers following your internal prioritization framework.
What you avoid:
You're not required to publish a compliance percentage, provide a French-language accessibility statement, implement the mandatory feedback mechanism with Rights Defender escalation, or maintain a multi-year accessibility improvement plan.
Technical requirements:
WCAG 2.2 AA includes about 50 success criteria across four principles. You test against these criteria using your chosen methodology. The standard allows interpretation flexibility. If you can show your implementation meets the success criterion's intent, you've achieved conformance.
Strategic advantage:
WCAG 2.2 AA conformance positions you for future expansion. If you later need RGAA compliance, you've already addressed most technical requirements. The gap is primarily documentation and process, not fundamental accessibility work.
Path B: RGAA 4.1.2 Is Mandatory
Choose this path if:
- You're a French public body (government agency, municipality, public hospital, university)
- You're a private company in France with more than €250 million average annual turnover in the last three years
- You operate public services of general interest (transport, energy, telecommunications, certain banking services)
- You provide products or services to French public entities as a vendor
What you implement:
RGAA 4.1.2 translates WCAG 2.1 AA into 106 testable criteria with about 300 defined test methods. Unlike WCAG's interpretive flexibility, RGAA prescribes exact testing procedures with pass/fail determinations.
Mandatory deliverables:
Your accessibility statement must appear in French on every digital service, accessible from every page. It includes your compliance percentage, audit date, test environment details, a complete list of non-compliant elements, and exemptions with disproportionate burden justifications.
You must display your compliance percentage publicly, typically on your homepage and in the footer. If you're below 50% compliant, you're classified as non-compliant. Between 50% and 99%, you're partially compliant and must list specific non-conformances. Only 100% conformance earns fully compliant status.
User feedback mechanism:
Provide an accessible channel for users to report barriers, with expected response timeframes (typically within one month). Your accessibility statement must include contact details for the Défenseur des droits (French Rights Defender) and explain the escalation process if internal resolution fails. The direct link to https://formulaire.defenseurdesdroits.fr/ must be published.
Multi-year improvement plan:
Publish and maintain a strategic roadmap documenting your accessibility efforts, assigned responsibilities, audit schedules, staff training programs, and progress tracking.
Timeline pressure:
Public websites faced a September 2020 deadline. Mobile apps and digital interfaces had a June 2021 deadline. If you haven't achieved compliance yet, you're operating in violation. Private sector organizations under European Accessibility Act requirements faced a June 28, 2025 deadline.
Technical differences from WCAG:
RGAA interprets WCAG criteria more strictly. For WCAG 1.3.1 (Info and Relationships), RGAA requires specific <label>, <fieldset>, and table markup patterns. For WCAG 3.3.2 (Labels or Instructions), RGAA mandates explicit <label> usage with no exceptions. For WCAG 4.1.2 (Name, Role, Value), RGAA provides detailed ARIA implementation rules that go beyond WCAG's general guidance.
Path C: Hybrid Approach for Market Entry
Consider this path if:
- You're planning French market expansion but haven't established operations yet
- You're in procurement discussions with French public entities
- You want to demonstrate accessibility maturity before legal requirements apply
What you implement:
Start with WCAG 2.2 AA conformance as your technical foundation. Add RGAA-specific elements incrementally: create the French-language accessibility statement template, establish the feedback mechanism infrastructure, and document your improvement roadmap even before it's legally required.
Strategic value:
This positions you as accessibility-mature in competitive procurement evaluations. French public entities increasingly evaluate vendor accessibility capabilities during selection, even when legal mandates don't yet apply. Demonstrating RGAA readiness differentiates your proposal.
Summary Comparison Matrix
| Factor | WCAG 2.2 AA | RGAA 4.1.2 |
|---|---|---|
| Legal status in France | Voluntary practice | Mandatory for covered entities |
| Test criteria | ~50 success criteria | 106 criteria with 300 test methods |
| Testing methodology | Flexible interpretation | Prescribed pass/fail procedures |
| Accessibility statement | Optional | Mandatory in French with exact format |
| Compliance percentage | Not required | Must display publicly |
| User feedback system | Recommended | Mandatory with Rights Defender link |
| Improvement plan | Internal only | Must publish multi-year roadmap |
| Non-compliance penalty | Varies by jurisdiction | Up to €20,000 per service annually |
| Update frequency | As needed | Within 3 months of major changes |
Your path depends on legal obligation, not preference. If you're subject to French digital accessibility law, RGAA 4.1.2 isn't negotiable. If you're not yet covered but planning French operations, starting with WCAG 2.2 AA and building toward RGAA creates a manageable transition path.
The technical work overlaps substantially. The real difference is documentation rigor, public transparency, and enforcement mechanism. Choose based on your legal status, then execute with precision.
