Accessibility

Accessibility statement

We are committed to making this website accessible to as many people as possible, aiming for WCAG 2.2 level AA, RGAA 4.1.2 and the EN 301 549 standard. This page sets out where we stand, what remains to be fixed, and how to report an issue to us.

  • Updated on 17 October 2026
  • Method: self-assessment, browser testing and axe-core

Conformance status

Partially conformant

Blocking and major issues have been fixed and no non-conformity is known to date. Testing with screen reader users remains to be done.

  • WCAG 2.2Target level AA
  • RGAA 4.1.2French framework
  • EN 301 549European standard

Improvements already in place

Thirteen fixes are in place and verified across the entire public website.

  • Page language declared and adapted to each language version.
  • Semantic structure (banner, navigation, main content and footer regions) and a skip link to the main content.
  • Text alternatives for informative images.
  • Keyboard navigation and a visible focus indicator.
  • Image enlargement dialogs operable by keyboard (close, focus return).
  • Respect for the system “reduce motion” preference.
  • Reinforced text contrast.
  • Layout adapted to small screens: no page scrolls horizontally at 320 px wide, and browser zoom remains allowed.
  • Navigation menus, mobile menu and FAQ usable with the keyboard, with their open or closed state announced.
  • Contact form: visible labels, autocomplete support, errors described in text and announced.
  • Tables wider than the screen can be browsed with the keyboard.
  • Search results (blog, FAQ, security) announced to screen readers.
  • Customisable text spacing (line height, letter, word and paragraph spacing) without loss of content.

Content not yet accessible

No non-conformity is known to date. One check remains to be done, tracked in our action plan.

  • Screen reader output: verified through the browser's accessibility tree and axe-core, with no defect found; testing with NVDA and VoiceOver users remains to be done.User testing to be done

Reporting an accessibility issue

If you encounter an accessibility barrier on this website, tell us which page it is on and describe the problem: we strive to respond as quickly as possible, and we fix anything that blocks use as a priority.

Report an issue

Preparation of this statement

Date prepared
21 May 2026
Last updated
17 October 2026, after the website redesign
Method
Self-assessment against the WCAG 2.2 AA, RGAA 4.1.2 and EN 301 549 criteria: code review, automated checks on every published page, browser tests (keyboard, display at 320 px wide, text spacing, calculated contrast ratios), axe-core and the browser's accessibility tree
External audit
None to date
Updates
As fixes are made