Accessibility statement

Accessibility is part of what “useful on a phone” means. A newcomer reading on a cracked screen on a cold bus stop, a parent with one hand free, a learner using a screen reader, a reader who does not see colour the way the designer does: the site is for them too.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the site, in both languages. We treat it as a standing commitment rather than a one-time audit; new pages and features are checked before they go live.

What the site does

• Structure. Every page uses semantic HTML: one main heading, a logical heading order, landmarks for navigation, main content and footer, real lists and real tables with header cells.
• Keyboard. Every link, button, form control, filter and lesson exercise can be reached and operated with a keyboard. Focus is always visible. A “skip to content” link is the first thing on every page.
• Language. Each page declares its language (fr-CA or en-CA). Where a phrase in the other language appears inside a page, for example in a lesson, it is marked so that screen readers switch pronunciation.
• Contrast and colour. Text and interface colours meet the AA contrast ratio. Colour is never the only way information is shown; status and categories also use text or shape.
• Text size and zoom. Pages reflow at 200% zoom and at 320 pixels of width without horizontal scrolling or lost content.
• Motion. The site has no flashing content. Subtle reveal animations and the mascot’s movement are disabled automatically when your device’s reduced-motion setting is on.
• Forms. Every field has a visible label, errors are described in text next to the field, and nothing is submitted by a timed action.
• Images. Meaningful images and illustrations have text alternatives. Decorative artwork is hidden from assistive technology.
• Audio and speech. Lessons offer optional audio and optional microphone practice. Both are additions: every exercise can be completed by reading and by keyboard, and the site explains how audio is handled before you turn on a microphone.
• Printing. Guides, checklists and the moving planner have print styles that remove navigation and show link addresses.

Known gaps

We would rather list them than pretend. As of the review date at the top of this page:

• Third-party content. Linked external sites, embedded maps and event pages on organizers’ sites have their own accessibility, which we do not control. Where a map is used, the same information is available in a list or table.
• Pronunciation practice relies on the browser’s built-in speech recognition, which varies by device and performs unevenly for some accents. It is optional and never required to complete a lesson.
• PDF or printable exports are generated from the page and have not yet been tested with every screen reader.
• Automated and assistive-technology testing has been done with a limited set of browsers and screen readers. We will widen it, and we welcome reports from people using tools we have not tested.

Reporting a barrier

Email info@repyyc.com with “Accessibility” in the subject line, or use the corrections form and choose “Accessibility”. If you cannot use the form, the email works just as well. We do not need your personal details beyond a way to reply.

Standards and law

This statement refers to WCAG 2.1 (W3C). We follow it as a matter of design, not only compliance, and will update this page when the site is assessed against a newer version of the guidelines.

Review

This statement is reviewed whenever a major section is added and at least once a year. The last-reviewed date is shown at the top.