Accessibility
Last updated: August 3, 2026
Commitment
Digital accessibility means making this site usable by everyone, including people with disabilities. It is considered during development rather than added afterwards.
This statement describes the real state of accessibility on the platform, including what has not been done yet.
Conformance status: no audit has been carried out
No accessibility audit, against RGAA or WCAG, has been conducted on this site to date. No conformance rate can therefore be declared, and none is claimed here.
Announcing a conformance rate would imply a measurement result that does not exist. This page will be updated once an audit has been performed.
The target standard is the current RGAA, corresponding to WCAG 2.2 level AA.
What has been implemented
The following are present in the code and can be verified by reading it:
- a skip link to the main content, first in the tab order on every page;
- semantic structure: header, named navigation, main content and footer are identified;
- form fields tied to real labels, with error messages linked to the field and announced;
- a visible, contrasting focus indicator that is never removed;
- the system "reduce motion" preference is honoured;
- native progress elements, so assistive technology reports the value;
- touch targets at least 44 pixels tall for buttons and primary actions;
- a light, dark or system theme, with the selected state announced rather than only coloured;
- each page's language declared in the markup, and a language switcher that keeps you on the same page.
- automated accessibility tests in continuous integration: axe-core's WCAG 2.1 and 2.2 level AA rules are run against the public pages in both languages, the course and lesson pages, the dashboard and the account page, in the light theme and the dark one;
- colour contrast for the three status colours computed from the stylesheet, as text and as a badge, on all three surfaces and in both themes;
- the administration pages included in that automated check — overview, content, accounts and audit trail — where they were excluded until 8 August 2026: they carry the densest data tables on the site, and are the surface least likely to be checked by hand.
Known gaps
The following are identified shortcomings, not yet addressed:
- no testing has been done with a real screen reader (NVDA, JAWS, VoiceOver);
- the automated tests cover only part of the criteria: they find a missing label or an insufficient contrast ratio, but cannot judge whether alternative text is apt, whether focus order matches reading order, or whether content makes sense read aloud;
- behaviour at 200% zoom and in text-only mode has not been verified;
- code blocks scroll horizontally, which can hinder reading on a small screen or at high magnification;
- the interactive quiz and lab components have not been validated with assistive technology;
- the learning content contains many English technical terms that are not marked up as such, which can affect screen reader pronunciation.
Feedback and contact
If you hit a barrier, report it using the contact address in the legal notice. Describe the page and the difficulty; these reports are treated as a priority.
We aim to respond within a reasonable time and, where relevant, to offer another way of reaching the information.
Escalation
If a report goes without a satisfactory response, you may contact the French Défenseur des droits through the online form on their website, or by post to Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07. There is no charge.
