Accessibility Statement

Draft — NOT REVIEWED

Written on 2026-08-05 by reading this website's source code and the tests that run against it. Nobody has reviewed it — not an accessibility specialist, not anyone who uses assistive technology, not the district. It is not a certification.

How accessible this site is

This site is partially conformant with WCAG 2.1 Level AA. Partially conformant means some parts do not fully conform to the standard, and the limitations below are why that is the strongest honest word available.

What is tested

Every public page is audited automatically against the live site — 40 routes today, every page in every language the site publishes. It runs on every change and again once a day, and reported no serious or critical problem on any route when it first ran, on 2026-08-05.

A skip link opens every page. Skipped heading levels and missing alt text block a district leader from publishing at all, rather than being reported afterwards. Contrast corrections are held in place by tests.

Known limitations

This is the part worth reading.

• No person has tested this site. There has been no screen reader walkthrough, no keyboard audit by a human being, no testing with people who have disabilities, no third-party audit. A machine cannot check whether alt text describes the image, or whether a page still makes sense read aloud.

• The audit does not block a bad release. It runs after a change is already live, so a failure means the version that failed is already serving the public.

• Only serious and critical findings fail the build. Minor and moderate ones pass, so some exist and have not been fixed.

• The page for an address that does not exist is blank if your browser does not run JavaScript. Why it behaves that way has not been settled.

• The administration consoles sit behind a sign-in the audit cannot pass, and are checked more narrowly instead.

• Video, registration forms and documents embedded from YouTube, Vimeo, Eventbrite, Zeffy and Google Drive are outside all of this. Tell us anyway if one of them blocks you.

How to report a barrier

If something on this site stops you doing what you came to do, tell us: Report an accessibility problem. The same link is in the footer of every page.

The form reaches the people who build this site, not the district: district leaders are member volunteers who cannot fix a keyboard trap. It promises no reply and no timeframe — a commitment nobody keeps is worse than none — but the report does reach someone who can act on it. It asks for a description of the barrier and an email address only if you want one used, and it works with JavaScript switched off.

What has not been settled

This is a self-assessment, prepared on 2026-08-05 by the people who build this site. There has been no third-party evaluation and no usability testing with people who have disabilities, and no date of last human review can be given because there has not been one.

Ontario's AODA and the Quebec accessibility framework may bear on a site like this one. Whether they do has not been determined, and this document makes no claim in either direction. They remain open questions.