RGAA 5 is coming: what does it mean compared to RGAA 4 and WCAG 3?
I’ve just come to read this article about a new version of RGAA coming this year and it made me think about what this really means for everyone who uses digital services. (Here’s the announcement from DINUM if you want to read it too: https://design.numerique.gouv.fr/articles/2026-03-02-rgaa5/)
RGAA 5 is expected by the end of 2026 and it brings real improvements. Here’s what stands out in practical terms:
What RGAA 5 adds compared to RGAA 4
1️⃣ Broader coverage beyond websites
RGAA 4 was primarily focused on traditional web pages. RGAA 5 widens the scope to include: mobile apps, documents (pdf, word documents), non-HTML content. This means accessibility checks apply more consistently across all digital touchpoints, not just the website.
2️⃣ Updated criteria aligned with WCAG 2.2
This brings improved keyboard navigation rules, enhanced guidance on hidden content, clearer requirements for focus order and content labeling.
These are subtle but impactful changes for end users, especially people with cognitive or hearing impairments.
3️⃣ Less ambiguity, more clarity
RGAA 4 could be hard to interpret for people new to accessibility. RGAA 5 aims to make criteria easier to understand and apply, which should improve the consistency of accessibility work across organizations.
4️⃣ Stronger regulatory support
With ARCOM as the designated authority and a dedicated tele-service for declarations, compliance will be easier to track and publish. This means more up-to-date accessibility information for users, not just a static PDF buried somewhere.
What it really means for users
People with disabilities will benefit from more holistic accessibility: not just web pages, also apps, forms, documents and services
Consistency across digital services: users won’t have to guess whether an app is accessible if the website is
More predictable communication: better declarations of accessibility, easier to find and understand
Less reliance on audit-only snapshots: RGAA 5 supports ongoing accessibility integration, not just one-time reporting
How RGAA 5 relates to WCAG evolution
RGAA 5 stays in the WCAG 2 universe, not moving to WCAG 3 yet because WCAG 3 is still a work in progress and not a regulatory reference in most countries.
RGAA 5 pushes accessibility further in a practical, user-centered direction.
Would you like to see included in RGAA 5 that isn’t mentioned yet?