RGAA (Référentiel Général d’Amélioration de l’Accessibilité, General guidelines for improving accessibility) is a French regulatory framework that exists in four versions (RGAA 1, RGAA 2, RGAA 3, RGAA 4). It designed to ensure that web content is accessible to everyone, including people with disabilities.

RGAA is published by the Interministerial Digital Directorate (DINUM) and is a continuation of Law No. 2005-102 of February 11, 2005, on equal rights and opportunities, which requires digital accessibility for public services.

RGAA 3 is based on the WCAG (Web Content Accessibility Guidelines), developed as part of the W3C process, an international collective of individuals and organizations working to provide a common standard for web content accessibility.

Benefits of digital accessibility through RGAA compliance testing

Web accessibility is a major political and societal issue: it aims to enable all people, regardless of their disabilities (visual, auditory, motor, cognitive, etc.), to access the content and functionality of a website or digital service. 

The benefits are many: 

  • legal compliance to avoid legal penalties,
  • improved user experience for all (especially the elderly and mobile users), 
  • improved search engine optimisation (SEO)
  • enhanced brand image by demonstrating a clear commitment to inclusion.

Who is the RGAA Aimed at?

The RGAA is primarily aimed at public sector bodies, in particular state administrations, local authorities and public institutions, which have a legal obligation to make their digital services accessible to all, in accordance with the Disability Act 2005. It also applies to certain private companies that provide public services, such as transport or healthcare providers, as well as companies that exceed regulatory thresholds (particularly in terms of turnover or workforce).

But beyond legal obligations, the RGAA also imposes a professional responsibility on web service providers: agencies, freelancers, developers, integrators, UX/UI designers, etc. All these players must ensure that the websites, applications, and components they deliver comply with accessibility requirements.

In this sense, the RGAA is both a regulatory framework and a digital quality tool, guaranteeing an inclusive experience for all users, including people with disabilities.

RGAA 1 & 2: Laying the Foundations of France’s Digital Accessibility Framework

The first version of the RGAA, directly inspired by the WCAG, was published in 2009. It marked an important step in the structuring of digital accessibility in France. The main purpose of this inaugural version was to translate the W3C’s international WCAG recommendations into an operational framework adapted to the French context. The goal was to provide a practical reference guide that could be used directly by web developers and web designers.

At the time, the 2009 RGAA 1 was intended exclusively for public administrations and services, in the context of the 2005 law on disability. The websites that had to be made accessible were those of ministries, local authorities, public institutions, etc.

The RGAA highlighted verifiable technical criteria and concrete test grids to assess compliance with the criteria, and proposed binary assessment models (using a compliant/non-compliant rating system), which facilitated audits.

The 13 main themes of the first version of the RGAA covered images, colors, tables, forms, navigation structure, scripts, all multimedia content, etc.

The second version of the RGAA, published in October 2009, maintained the WCAG 2.0 criteria and the basic structure of the RGAA 1, but incorporated many more tests to verify and test compliance.

The two first versions of RGAA laid the foundations for the French digital accessibility framework, using a pragmatic and operational approach aligned with international standards. The adoption of good accessibility practices in government agencies has been greatly accelerated and facilitated by RGAA.

RGAA 3: A Major Overhaul for Web Accessibility

Version 3 of the RGAA, initially published in 2015, marks a significant development in the French regulatory framework for web accessibility. This overhaul aimed to:

  • Modernize public service websites and applications

  • Clarify and specify accessibility criteria,

  • Align the RGAA with international WCAG 2.0 standards.

Full Alignment with WCAG 2.0

RGAA 3 adopts the structure and founding principles of the Web Content Accessibility Guidelines (WCAG 2.0): Perceivable, Operable, Understandable, and Robust (POUR).

This alignment ensures better international compatibility and facilitates the adoption of accessibility guidelines for both developers and experts.

Redesigned Structure, Clarified Criteria

With this new version, the language of the reference framework has become more consistent, clear, and accessible. Key changes include:

  • New numbering of criteria

  • Removal of redundancies

  • Reorganization of the 13 themes (images, navigation, forms, etc.)

  • Formulation focused on technical understanding and practical applicability

Introduction of Compliance Levels

RGAA 3 introduces a hierarchy of accessibility criteria (A, AA, AAA) according to their impact. This system of compliance levels makes it easier to prioritize the necessary corrections.

Practical information sheets have also been added for specific cases, such as:

  • Dynamic content

  • CAPTCHAs (page 28)

  • Third-party content (videos, widgets, etc.)

Enhanced Tools and Documentation

To support implementation, RGAA 3 offers:

  • Pre-filled audit spreadsheets

  • Detailed test guides for each criterion

  • Open source tools to facilitate automated checks

  • Regularly updated online documentation.

These resources are intended to simplify the adoption of the framework in digital projects.

Consideration of Modern Technologies

RGAA 3 is designed to better integrate modern web technologies, including:

  • HTML5, ARIA, dynamic JavaScript,

  • single-page web applications (SPAs),

  • interactive components and dynamic menus.

Version 3.0.1, released in 2020, further enhances the readability and applicability of the framework with the addition of best practices — without adding to the technical requirements.

RGAA 4: What are the Changes in the Latest Version of the Reference Framework?

Version 4 of the RGAA was published in September 2019 and represents a significant update. It takes into account the international WCAG 2.1 recommendations published by the W3C in 2018 and realigns the French reference framework accordingly.

Success Criteria

RGAA 4 incorporates the 17 new success criteria introduced by WCAG 2.1. These additions provide better coverage of the needs of users with disabilities on mobile devices, with criteria related to screen orientation, complex gestures, and zoom. The guidelines also take greater account of cognitive impairments and enhanced visual accessibility needs, particularly through text spacing and contrast. All RGAA criteria are now explicitly linked to their equivalents in the WCAG. This makes the guidelines easier to read and facilitates interoperability with international guidelines.

Special Attention to Dynamic Components

With the rise of modern interfaces (JavaScript, SPAs, modals, sliders, etc.), RGAA 4 introduces more stringent requirements for interactive components. The aim is to ensure smooth keyboard navigation, correct management of ARIA roles, and consistent interpretation by screen readers. Modals, drop-down menus, carousels, and dynamic notifications are now subject to more extensive testing.

This change ensures that rich interfaces remain accessible to all, even in complex web environments.

New Documentation and Related Tools

The publication of RGAA 4 was accompanied by a complete overhaul of the documentation. Each criterion is now associated with specific unit tests, concrete examples, and documented special cases.

This approach promotes a better understanding of the requirements for developers, auditors, and UX designers alike. In addition, practical tools such as audit grids, compliance declaration templates, and best practice guidelines are available. This documentation aims to make accessibility more operational and easier to integrate into web projects.

Focus: Are CAPTCHAs Accessible?

A CAPTCHA (Completely Automated Public Turing Test to tell Computers and Humans Apart) is a mechanism commonly used to differentiate between human users and robots. However, most traditional CAPTCHAs pose major accessibility issues, as they are often unreadable for people with low vision or blindness and difficult for users with cognitive or motor impairments. Their use often violates RGAA criteria. Traditional CAPTCHA providers such as Google reCAPTCHA and hCaptcha use visual and manual image recognition tasks to verify people’s identities.

Friendly Captcha: a RGAA-Compliant Solution

Friendly Captcha is positioned as a respectful, modern alternative to traditionnal CAPTCHAs. Rather than relying on traditional user interaction (clicking on images, entering text, etc.), this solution uses a invisible cryptographic puzzle that is solved in the background while the user interacts naturally with the page.

Friendly Captcha was designed from the outset to be compatible with accessibility standards (RGAA, WCAG). It requires no complex interaction from the user. Verification is made invisibly in the background, meeting the requirements of an inclusive web.

To check the accessibility of your website or web application for free and in a single click, Friendly Captcha has developed the WCAG Checker. This online free tool allows you to check whether your website is accessible.

Is Your Website Accessible?​
With the WCAG Checker from Friendly Captcha, you can easily check your website for accessibility Issues. Find out all you need to know about making your website WCAG compliant and accessible.​

Conclusion: Importance of Digital Accessibility and RGAA for an Inclusive Web

RGAA (Référentiel Général d’Amélioration de l’Accessibilité) is an essential framework for ensuring the digital accessibility of public services in France.

With the evolution of RGAA versions, particularly versions 3 and 4, website and application compliance is becoming clearer, more structured, and better suited to modern technologies. The RGAA is not limited to a legislative framework; it represents a real lever for ensuring an inclusive and accessible web experience for all, particularly people with disabilities.

Adopting the RGAA is not just a legal obligation, but also improves the user experience and enhances the brand image of organizations. An accessible website benefits all users, while optimizing search engine optimization (SEO) and complying with international standards such as the WCAG. To help you with this process, free resources and tools are available on the official government website.

It is therefore essential that all web stakeholders, whether public administrations or private service providers, take responsibility for digital accessibility to contribute to a more inclusive internet.

FAQ

 The RGAA is essential because it provides a framework for digital accessibility for public services in France. It ensures that all citizens, including people with disabilities, can navigate, understand, and interact with online content. It is a legal obligation under the February 11, 2005 law on equal rights. Failure to comply with the RGAA may result in penalties, appeals, or complaints of digital discrimination.

 The WCAG (Web Content Accessibility Guidelines) are international standards defined by the W3C. The RGAA is their adaptation to the French regulatory context. It incorporates the main principles of the WCAG (perceptible, usable, understandable, robust) while providing concrete and applicable tests for project teams. The RGAA is therefore both legally binding in France and operational for web professionals.

The RGAA applies to all web technologies used in the design of a website or application. This includes:

  • HTML5, CSS, JavaScript,

  • ARIA (Accessible Rich Internet Applications),

  • SPAs (Single Page Applications), as well as dynamic components such as modals, sliders, drop-down menus, etc. It also takes into account the integration of third-party content and mobile accessibility constraints.

Yes. Since 2019, organizations subject to accessibility requirements must publish a declaration of compliance, or face administrative penalties. The regulatory authority (DGAFP or CSA, depending on the type of organization) may impose fines and require compliance.

But beyond penalties, poor accessibility damages brand image, user satisfaction, and search engine optimization (SEO).

With cybersecurity threats on the rise, organizations need to protect all areas of their business. This includes defending their websites and web applications from bots, spam, and abuse. In particular, web interactions such as logins, registrations, and online forms are increasingly under attack.

To secure web interactions in a user-friendly, fully accessible and privacy compliant way, Friendly Captcha offers a secure and invisible alternative to traditional captchas. It is used successfully by large corporations, governments and startups worldwide.

Want to protect your website? Learn more about Friendly Captcha »

Protect your enterprise against bot attacks.
Contact the Friendly Captcha Enterprise Team to see how you can defend your websites and apps against bots and cyber attacks.