Accessibility
The target is WCAG 2.1 level AA. Every build checks this site against it. No independent audit has been done.
Last updated 2026-09-25.
The standard we aim at
WCAG 2.1 level AA, in both official languages. The Accessible Canada Act is the reason a federally regulated buyer asks for it.
Accessibility and bilingualism are the same commitment here. A page that works only in English fails half the people who must use it.
What every build checks
- axe-core, WCAG 2.0 and 2.1, levels A and AA
- Every page, at 1280 px and at 320 px.
- One h1 per page, no skipped heading level
- A screen reader gets a usable outline.
- No horizontal scrolling at 320 px
- WCAG 1.4.10. Tables scroll inside their own region.
- Every internal link and anchor resolves
- No dead link in either language.
- Language switcher pairs point back
- Each page reaches its counterpart, and returns.
- html lang matches the page
- en-CA or fr-CA, so pronunciation is right.
The check runs in a real browser at two widths and fails the build on any violation. It lives in site/scripts/check-site.mjs.
Decisions behind the pages
- No JavaScript required
- Every page works with scripting off. The menu is a native details element.
- Visible focus
- A 2 px ring with a 2 px offset on each interactive element, kept in forced-colours mode.
- Colour is never alone
- Status words carry the meaning. Removing colour removes nothing.
- Motion respects the setting
- Transitions stop when the system asks for reduced motion.
- Text reflows
- French runs about 20% longer than English. Layouts wrap; nothing is truncated.
What we do not claim
An automated check is not an audit.
axe-core finds a share of WCAG failures, not all of them. No independent auditor or assistive-technology user has assessed this site.
The learning platform has no learner screens built yet, so it cannot be audited. Its conformance is a target, not a result.
There is no video or audio content yet, so there are no captions or transcripts to judge. When that content exists, both will ship with it.
Tell us about a barrier
Write to hello@crediteris.com in either official language. Name the page and what happened.
We answer within five business days, and we say what we will do and when.