What is measured, what is not, and what is missing

The audio component your readers use, on your own site.

This is the most worked-on scope, because it is the product. Play, pause, seeking and speed are keyboard-operable, focus is visible, position is announced to screen readers, and the listener has their own settings: text size, a dyslexia-friendly typeface, reinforced contrast.

The proof: The client area shows, account by account, the list of what is actually active on your player, with the RGAA reference for each aid. That list is what feeds the declaration template, not a brochure.

The caveat: The player is one brick of your site, not your site. Its conformance says nothing about your navigation, your forms or your editorial images.

The pages you are reading right now, with no account.

Swept at every revision by a real browser: 35 pages on the last pass, zero gaps of critical, serious or moderate severity. A set of checks also reads the source at every commit and refuses regressions we have already met: a skip link leading nowhere, a heading-level jump, a scrolling region unreachable by keyboard, text whose opacity falls below the contrast threshold.

The proof: The command is public and the list of audited pages is in the repository. You will get the same result we do: node scripts/audit-accessibilite.mjs.

The caveat: An automated sweep does not replace an audit. See «what the measurement does not say» below, which is the most important section on this page.

The screens behind authentication, used by your teams.

Built with the same components and the same design system as the public site, so it inherits its contrasts and its structure. The accessibility report, the most consulted screen on this subject, is keyboard-operable and readable by a screen reader.

The proof: None, and that is the point to take away: the automated sweep stops at the authentication door. We therefore present no figure for this scope.

The caveat: It is our largest known blind spot. It is written here rather than passed over in silence.

It catches what can be computed: a contrast, a missing attribute, a heading order. It cannot judge whether an alt text describes its image well, whether the reading order makes sense, or whether an instruction is understandable. Those criteria need a human, and nobody has run them across our site.

A declaration of conformity presupposes a formal audit, criterion by criterion, on a defined sample, dated and signed. It has not happened. As the law stands, this site must be considered non-compliant in the RGAA sense: not because everything on it would be inaccessible, but because conformity is only declared with an audit behind it.

A screen reader cannot be simulated. Until we have run NVDA, JAWS and VoiceOver over the main journeys, we cannot say the site is usable with them, only that it is built to be.

The client area, because it sits behind authentication. And the API reference, which goes through the same access control. They are not counted in the announced figure, and announcing it otherwise would inflate the coverage without improving anything.

It covers the audio component, not your whole site, and it says so in its own text. We are not a consultancy: have your conformity validated by a professional before you publish it.

Press Tab from the top of this page.

What should happen: The first stop should be a «Skip to content» link that appears. Every stop after it should be visible, ringed in green. You should be able to reach any link without ever guessing where you are.

Press Ctrl and + (Cmd and + on a Mac) until the browser reads 200%.

What should happen: The text should reflow into one column, nothing should be cut off, and no horizontal scrollbar should appear at page level.

In your browser's content settings, deny scripts for this domain, then reload.

What should happen: Every public page must stay readable and navigable. This is the test that caught us out on 5 August: two whole pages displayed blank, and we only saw it by doing it.

Turn on «reduce motion» in your system's accessibility settings, then reload.

What should happen: No more fade-ins, no more breathing on the first screen. If something still moves, it is a gap: write to us and it goes ahead of the rest.