We’ve been waiting for it for a while now, but here we are, the date is getting close, announced for December 2026 (with a decree to make it official sometime in 2027): RGAA 5 is coming.
It has to be said that the last version, RGAA 4.1.2, was last updated in April 2023. And in the digital world, that’s more than a billion years.
So, for those of you who don’t read us every day (we’re shocked, but we forgive you), the RGAA is the Référentiel Général d’Amélioration de l’Accessibilité (General Accessibility Improvement Framework), used to assess whether a digital service is compliant. Roughly speaking, the French equivalent of the WCAG.
Let’s go through together what this new RGAA 5 will change, since DesignGouv (opens in new window) has finally given a bit more information about what lies ahead.
What changes with RGAA 5
-
The most important point, first of all, is better coverage of the different digital media. RGAA 5 casts a wide net and will make it possible to audit any type of digital medium, whether websites, mobile apps or office documents. Each of these digital media will have its own framework and technical tests suited to it. So we get 3 frameworks in 1.
-
The accessibility statement will have to be more transparent, in particular by putting forward the means of contact, so that blocking issues can be explained directly to the people concerned.
For public services, this accessibility statement will have to be filed, using a new online accessibility statement service where they will fill in a form and which will host their accessibility statement directly. This process will make the work of Arcom easier: since 2023, Arcom has been in charge of making sure public service websites meet their accessibility obligations (statement, compliance status shown on the site, multi-year plan and action plan), and it will still be able to issue formal notices, impose fines, and so on.
-
The “partially compliant” label will still exist for sites that meet at least 50% of the criteria, but the subtlety is that this 50% threshold for “partially compliant” also requires that no major blocking accessibility issue be present. This notion of blocking non-compliance will force sites to switch to non-compliant if the audit finds a non-compliance deemed blocking, whatever the site’s overall rate. For example, a site that currently holds a partially compliant label with an 80% compliance rate will become non-compliant if it has animations that there’s no way to stop. The aim of this constraint is to push designers and developers to fix major blocking criteria quickly.
The concept of an average compliance rate, which gave an average score across all pages, is also being dropped.
-
The multi-year accessibility plan, which documents how accessibility is organised and handled, now has a specified format. It will no longer be just free text, but a structured format.
-
And above all, what matters in this new RGAA 5 is the arrival of 40 new criteria, aligned with WCAG 2.2 and the European standard EN 301 549 V4.1.1, which therefore add criteria for elements left aside until now, such as chats, captchas or overlays (hello, so-called accessibility tools that let you change the colour and size of the text in CSS and are sold at a premium to pass sites off as accessible when they weren’t at all).
Can we prepare for it?
We imagine that if your site already takes RGAA 4 into account, you’re already on the right track and there’s nothing much to be scared of. Above all, you’ll need to plan to update your accessibility statement to bring it in line with the RGAA 5 statement, but a statement made before its publication will remain valid for 18 months (up to 3 years after its date): enough time to make the adjustment.
On the other hand, if you weren’t already aligned with RGAA 4, we can only advise you to give us a call. We can carry out an accessibility pre-audit based on RGAA 4 to highlight all the problems your users with disabilities run into, and we’ll complete it as soon as RGAA 5 goes live.
If you really want to get ahead, WCAG 2.2 (opens in new window) is already available and probably covers all the RGAA 5 criteria for websites (and maybe even more).
You can also take a look at the Luxembourg frameworks, which already separate the media the way RGAA 5 will: RAWeb 1.1 (opens in new window) for websites, RAAM 1.1 (opens in new window) for mobile apps and RAPDF 1.1 (opens in new window) for PDF documents.
Nothing to be afraid of
In the end, the arrival of RGAA 5 is more in step with how digital services are actually used today. The criteria are revised, but above all they’re reorganised and simplified, with precise tests to make sure sites respect accessibility not only from a technical angle, but also from a usage angle.
Sources
- DINUM, DesignGouv, « Ce qui change avec le RGAA 5 », 3 November 2026 (opens in new window), read on 19/11/2026
- DINUM, DesignGouv, « Nouvelle version du RGAA », 2 March 2026 (opens in new window), read on 19/11/2026
- RGAA 4.1.2, « Mis à jour le 18 avril 2023 » (opens in new window), read on 19/11/2026
- ETSI, EN 301 549 V4.1.1 (opens in new window), read on 19/11/2026
- W3C, WCAG 2.2 (opens in new window), read on 19/11/2026