Testing

RGAA Assistant: testing a page with the extension, and what it leaves to the tester

6 min read
Mikhail ShaymardanovWeb Quality and Accessibility Expert

The RGAA Assistant puts all 258 tests of France's accessibility checklist into the browser of whoever is checking a page. That checklist is the RGAA, France's official accessibility standard. The free Chrome and Firefox extension walks through the tests one by one and highlights what each one targets on the page. The verdict stays human: the tester records each result, and the extension rolls it up to the criterion.

Two criteria tested on a ceramics shop


#What the RGAA Assistant extension does on a page?

The extension runs the tests of the RGAA one criterion at a time. Its publisher describes that standard as a hands-on adaptation of WCAG 2.1, the international accessibility guidelines. It installs from the Chrome Web Store or from Firefox Add-ons, where it's listed under its French name, Assistant RGAA. The name sounds official, and its history backs that up: it was first built for DINUM, the French government's digital agency, which later endorsed it. Boscop, the company behind it, maintains it today.

The extension exists only in French, so its screenshots show French labels, translated here as they come up. Version 2.1.2 opens in Chrome as a side panel or in a separate window. We opened it on Atelier Lune, a demo ceramics shop also in French, and at first nothing happened. The panel shows the Images theme, every criterion reads “NT” for not tested, and the page stays untouched. That's how the standard is organized: 106 criteria in 13 themes. Each criterion asks one question about the page, and its tests split it into checks.

Checking the first box wakes the page up. With test 1.1.1, four images get a red outline, each followed by a tag that shows its code. Along the right edge, a thin orange strip marks where each outline sits.

Screenshot: on the left, the Atelier Lune home page in Chrome, with a red outline and a code tag around the banner of bowls, the Celadon bowl, the Sand cup and the Cobalt cup, and no outline on the logo; on the right, the extension's panel in French, criterion 1.1 open, test 1.1.1 checked.Marker 1. The four images outlined in red with their code tags: the banner of bowls, the Celadon bowl, the Sand cup and the Cobalt cup. Marker 2. Test 1.1.1 checked in the extension's panel.
Once test 1.1.1 is checked in the panelmarker 2, four Atelier Lune images get a red outline and a code tagmarker 1; the logo, alone inside a link, stays unframed.

Under the test, the “Instructions” section quotes the official method word for word. It says to find the images, decide whether each one carries information, then look for its alternative, the text that replaces it.

Screenshot: the extension's side panel in Chrome, in French, Images theme, criterion 1.1 open, test 1.1.1 checked with the C, NC, NA and NT buttons, its instructions expanded, and “Tests actifs : 1.1.1” (active tests) at the bottom.Marker 1. The checked box of test 1.1.1. Marker 2. The “Instructions” section, the test's official method.
As soon as the box of test 1.1.1 is checkedmarker 1, the panel expands the official instructionsmarker 2 and shows the four result buttons.

#How to run an RGAA test on a page with the extension?

A test takes three moves. Until its box is checked, it has no result buttons.

  1. Check the test's box. The page outlines what it targets, and the instructions appear.
  2. Judge each outline against those instructions.
  3. Pick the result: compliant (C) or non-compliant (NC). NA stands for not applicable, NT for not tested.

#Do the images on the page have a text alternative?

With test 1.1.1, the extension outlines the images in scope and shows their code, right or wrong: sorting them out is the tester's job. On Atelier Lune, we got four red tags. Only a missing alt, the usual home of the alternative, shows struck through, though other attributes can carry it. The logo, alone in its image link, has no outline: its alternative names the link, so it's judged with the links.

Screenshot: under the banner of bowls and under the three Atelier Lune products, four red tags from the extension show the code of each image.Marker 1. The tag of the banner of bowls: img, empty alt. Marker 2. The tag of the Celadon bowl: img, alt struck through. Marker 3. The tag of the Sand cup: img, alt “image”. Marker 4. The tag of the Cobalt cup: svg, aria-label in French for “Blue cup, 25 cl”, role img, alt struck through.
Every tag is red: an empty alt on the bannermarker 1, a struck-through alt on the Celadon bowlmarker 2, alt “image” on the Sand cupmarker 3. The Cobalt cupmarker 4 also has a struck-through alt, even though it carries its name, “Tasse bleue, 25 cl”.

The banner, a mood shot, has alt="": that empty alt marks it as decorative, judged with the decorative images. The Sand cup has alt="image". The word says nothing about the cup, yet an alternative exists, so this test passes; its accuracy belongs to the relevance criterion.

The Cobalt cup throws people the first time. Its photo sits inside an <svg> graphic, which role="img" declares an image. An aria-label names it in French: “Tasse bleue, 25 cl”, a blue 25 cl cup. Its tag still strikes through alt, which the extension looks for on every outlined image. The method expects none on this kind of image, though, so the strike-through is no failure, and the cup is compliant.

That leaves the Celadon bowl, with no alt. Its photo shows what the customer is buying, so it carries information, and without a text alternative it fails the test on its own. We clicked “NC”, and the criterion switched to “NC” at once. A “C” here would have left it at “NT”, since its 7 other tests were still untested.

Your images don't need alternative text

#Do the page headings follow a meaningful hierarchy?

Under the RGAA, jumping from heading level 1 to level 3 is discouraged, yet it isn't a failure as long as the heading hierarchy stays consistent. With test 9.1.1, the panel lists the headings with their levels: 1 Céramiques faites main (handmade ceramics), 3 Nos bols (our bowls), 2 Livraison (shipping), 2 Contact. No line in red, no gap flagged. “Livraison” isn't a regular heading tag, only a block the code declares a level 2 heading, yet it counts as one for both the standard and the extension.

Screenshot: on the left, the Atelier Lune page, where “Céramiques faites main”, “Nos bols”, “Livraison” and “Contact” are outlined in red and “Nos tasses” has no outline; on the right, the extension's panel in French, open on the heading hierarchy of test 9.1.1.Marker 1. The “Hiérarchie de titres” (heading hierarchy) list: 1 Céramiques faites main, 3 Nos bols, 2 Livraison, 2 Contact. Marker 2. The text “Nos tasses” (our cups), with no outline on the page.
The panel lists four headingsmarker 1, with “Nos bols” at level 3 right under level 1 and no gap flagged; “Nos tasses”marker 2, a plain bold block, gets neither an outline nor a line.

The instructions ask the tester to check “that the hierarchy between the headings is relevant”. The official glossary allows the jump, and the bowls section belongs under handmade ceramics, so this test is compliant.

Here's the catch: the list looks complete. “Nos tasses”, the cups section, displays in bold, as large as “Nos bols”. It's only a plain block of text, though, and the extension neither outlines nor lists it. The tester catches it at test 9.1.3, which requires any text that works as a heading to be coded as one. That test fails, and the headings criterion goes to “NC”.


#What's left to judge, and what an RGAA checker finds on its own?

No automated tool covers the whole RGAA. In an audit last updated in 2018, the UK government's accessibility team planted 142 barriers on a page. The best of 13 tools found 40% of them on its own. In version 2.1.2 of the extension, 61 of the 258 tests show only their instructions, with no marker on the page and no tool. Those take the keyboard, zoom, a screen reader or a careful eye. Visible focus is one of them: the outline or background that marks the element reached by keyboard. Text that has to stay readable at 200% zoom is another.

Even where the extension draws an outline, it doesn't give the verdict. The W3C, the body that writes the web's standards, says so of every evaluation tool: none of them checks everything automatically, and human judgment is still required. WebAIM's WAVE extension says it too, even on a page where it finds zero errors. On Atelier Lune, the four outlined images got their verdict only after we sorted them.

An automated scan, for its part, finds its share without a single checkbox.

The extension keeps what's left to judge in front of the tester, by design: Boscop built it for people who run audits. The results, recorded criterion by criterion, add up to an audit's findings.

Screenshot: the extension's panel in French on the Images theme, criterion 1.1 marked NC in red and criteria 1.2 to 1.9 marked NT.Marker 1. The “NC” status of criterion 1.1, in red.
One test recorded as non-compliant is enough: criterion 1.1 shows “NC”marker 1, and the other image criteria stay untested.

On Atelier Lune, we recorded each result, and the extension carried it up to the criterion. Images and headings both went to “NC”, each because of a single test, and every other criterion is still waiting its turn.

Website accessibility audit: cost, quotes and how to choose an auditor

For a live page, the Includdy scan lists the non-conformities it detects on its own, with no box to check. Its manual tests, headings and images included, then suggest a verdict for each element, which the tester confirms or corrects.


Share this article

Frequently asked questions

Not yet: the extension supports versions 3 and 4 of the standard, up to 4.1.2. The next version is scheduled for December 2026, and a decree will make it official the following year. It adds 40 new criteria to take in WCAG 2.2 and the European standard EN 301 549.

Until then, version 4.1.2 stays in force, and DINUM, the French government's digital agency, asks teams not to pause or postpone work based on it. The transition is covered in our article on RGAA 5.

Yes: its contrast analyzer computes the ratio between two colors, typed in as a hex code or a color name, or picked from the page. For an icon or a thin border, type in the color from the CSS instead: picked from the page, it can land on a pixel that screen smoothing has made paler (see checking non-text contrast).

For a transparent color or one written in another CSS format, our contrast checker accepts every format, handles transparency and suggests nearby shades that pass. To read the ratio of text right on the page, Chrome DevTools shows it too.

Yes, it's free, and it installs without admin rights on the computer.

On its Chrome Web Store listing, the publisher states that it collects and uses no data.