Standard we target
We target level AA of the Web Content Accessibility Guidelines (WCAG) 2.1, the W3C international standard. It is the level referenced by the Accessible Canada Act and by the Government of Quebec SGQRI 008 standard.
Conformance level reached
Partially conformant
This site is partially conformant with WCAG 2.1 level AA: the limitation listed below is the only known non-conformance.
How we assessed it
Automated audit with axe-core (the engine behind axe DevTools) on the live pages, then a manual criterion-by-criterion review of all 50 level A and AA criteria on the application: keyboard paths, contrast, reflow at 320px and 200% zoom, text spacing, reading order, forms and status messages, content on hover, language of parts.
Pages assessed
- Home
- Services
- About
- Plan page
- Published press release template
- Contact form
- Media upload form
What we fixed
Following this audit, the following corrections were deployed:
- Colour contrast raised to at least 4.5:1 for body text and 3:1 for interface elements, across every page assessed.
- Alternative text added to content images; purely decorative images carry an empty alt attribute so screen readers skip them.
- Heading hierarchy corrected: one h1 per page and no skipped levels.
- Visible keyboard focus indicator on every link, button and form field.
- Explicit labels on all form fields, including the file upload control and the mobile menu search.
- A skip link that jumps straight to the main content.
- Accessible names added to the share buttons, which previously showed only an icon.
- Background videos can be paused, and do not start when the system asks for reduced motion.
- Form field borders raised to at least 3:1 so every field is perceivable.
- Error messages linked to the field they concern and announced to screen readers.
- Upload progress and the list of chosen files are announced without moving focus.
- Contrast of the chat assistant launcher corrected on our side.
- Media carousel navigation operable from the keyboard.
- Video subtitles loaded into the player whenever a subtitle file (.srt) is attached to the release.
- Contact fields identified for browser autofill.
- Language marked on language-switch links and on any content shown in the other language.
- A single main heading per page, even when the release contains one.
- Chat assistant placed in a named landmark, with named buttons.
Known limitations
Despite our efforts, the following are not yet conformant. We document them openly and are working to resolve them.
- Anti-bot check (reCAPTCHA)
- The anti-bot check on forms relies on a Google component that can present a visual puzzle, a recognised barrier for some users.
- A provider with no visual puzzle is ready to be enabled (Cloudflare Turnstile).
Content submitted by our clients
The body of a release is written by the issuing organisation. The platform nonetheless guarantees: alternative text on every image (caption, otherwise the release title), subtitles displayed in the player when a subtitle file is provided with a video, and a normalised heading hierarchy. Our editorial team reviews every release before publication.
Report a problem
If you hit a barrier on this site, write to us: describe the page and what blocked you. We acknowledge within 2 business days and aim to respond substantively within 10 business days.