ACCESSIBILITY STATEMENT
Accessibility:
What works, and what does not yet
A civic safety network that some people can't use isn't doing its job. This page explains how accessible this presentation site is today, how we checked, and where it still falls short.
Partial conformance with WCAG 2.2, Level AA
This site is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. It partially conforms: our automated checks report no violations, but a few requirements are not met yet. They are listed below, with what we plan to do about each.
We do not claim Level AAA. This statement is based on our own testing. The site has not yet been audited by an outside specialist, or tested by people who rely on assistive technology every day.
What we tested, and how
- Automated checks. We ran the axe-core 4.14 testing engine on every page, in English and in French, at desktop and phone widths. It reported no violations.
- Keyboard. Every menu, link and button, the audio player and the app-screen lists can be used with the keyboard alone, and the focus is always visible.
- Names and language. Buttons, images and controls have names in both languages, and changes such as switching language are announced. We checked this by reading what the browser exposes to assistive technology, and then with a short screen-reader check (next item).
- Browsers and devices. Testing was done in a Chromium-based browser at desktop and small-phone sizes. Safari, Firefox and real devices are not yet checked systematically.
- Screen reader. A short VoiceOver check on a Mac passed on six key points: the skip link, French being read in French, a dropdown menu, the play and pause names on the audio player, the transcript link, and the announcement when an app screen changes. The rest of the site, and other screen readers, have not been checked with one.
What the site does for you
- A skip link on every page, and a clear page structure with headings and landmarks.
- Menus and controls that work from the keyboard, with a visible focus ring.
- Text and controls with enough colour contrast, and tap targets big enough for a finger.
- Full English and French versions, including the names that screen readers speak.
- A transcript for every audio overview.
- Captions on the English videos and the French presentation video, and a written description of every video.
- App-screen pages that work on small screens, without asking you to switch to a bigger one.
- Less motion if your device asks for it: no smooth scrolling and no looping animation.
What does not work yet
These are the parts we know do not meet WCAG 2.2 AA, or only partly meet it.
- WCAG 1.2.5 · AA
No spoken audio description for the videos
The scenario videos tell short stories mostly in pictures. A written description of each one is on the Intro page (“What happens in each video”), but there is no spoken audio-description track yet.
- WCAG 1.2.2 · A — limitation
French scenario videos use open captions
In French, the scenario videos have French captions built into the picture (translated from the English speech). They cannot be turned off, resized or restyled. The English videos use captions that the player's CC button can switch off.
- WCAG 1.2.3 · A
Text shown inside the videos
Each video begins with an intro title card. Its text is not yet repeated in the written descriptions.
- WCAG 3.1.2 · AA
A few labels are still in English on French pages
Some short labels (for example technical tags on some pages) are not yet translated, and are not marked as English for screen readers.
What we plan to do
- Test more of the site with VoiceOver (on Mac and iPhone), and with NVDA on Windows where possible, then fix what we find.
- Add the intro-card text to the written video descriptions.
- Translate the remaining labels, or mark them as English.
- Look into adding spoken audio description to the scenario videos.
- Check Safari, Firefox and real phones.
Something not working for you?
If you meet a barrier on this site, or need a page in another format, write to frederic.robert.parenteau@gmail.com. Tell us the page and what you were trying to do. We read every message and aim to reply within five business days.
You can also ask for any transcript or description as plain text.
Technical notes
This site is built with HTML, CSS and JavaScript only, and needs no plug-ins. Switching to French, the phone menu and the players need JavaScript turned on. The standard we work to is WCAG 2.2 (W3C).
How this site treats your information is explained in our privacy notice.
Prepared on October 9, 2026. We will update this statement after the next round of testing.