Accessibility
Accessibility at VerbaNorth
We want VerbaNorth to be usable by everyone preparing for a Canadian language test, regardless of ability or assistive technology. This statement describes what we support today and where we're still improving.
What we support
- Keyboard navigation — every page can be navigated without a mouse, with a visible focus ring and a "Skip to main content" link that appears on first tab.
- Screen readers — semantic headings, landmark regions, labelled controls, and descriptive names on interactive buttons.
- Dark mode & contrast — a light/dark theme toggle, with text colours chosen to meet WCAG AA contrast in both modes.
- Responsive layouts — pages reflow cleanly from large desktops down to small phones, with touch-friendly targets on mobile.
- Reduced reliance on colour alone — status and feedback use text and icons alongside colour.
- Spell-check left on in the Writing Lab, so misspelled words are flagged as you type — mirroring a real exam environment.
Known limitations
We're honest about what isn't done yet:
- Listening test audio has no captions or transcripts. Listening practice depends on un-scripted audio comprehension, so captions would defeat the exercise. If you rely on captions, the Reading, Writing, Speaking, and Vocabulary tools remain fully usable.
- Some interactive charts (progress trends, score reports) convey information visually; we provide the underlying numbers in text alongside them, but the charts themselves are not yet fully described to screen readers.
- AI feedback is generated text and may occasionally be formatted inconsistently for assistive technology.
VerbaNorth is an independent practice platform. Practice scores are estimates only and are not official test results.
Standards we aim for
We target WCAG 2.1 Level AA as our baseline. We test with keyboard-only navigation and screen readers, and we treat accessibility regressions as bugs.
Get in touch
If you hit an accessibility barrier on VerbaNorth, please tell us — your report helps us fix it faster. Email [email protected] or use the contact page, and describe the page and what went wrong.
Last reviewed: June 2026