Accessibility
This site is built and tested to WCAG 2.2 Level AA. This page says what that means in practice, what is checked automatically on every change, and what has not been done.
What is tested, on every change
Accessibility here is a build step rather than an annual review. The following run together and any failure stops the change:
- axe-core across 26 pages, against the WCAG 2.0 A and AA, 2.1 A and AA, and 2.2 AA rule sets, plus the best-practice set. Currently zero violations.
- Reflow at 19 widths, from 320px to 1440px, checking that no page scrolls sideways and no content is lost.
- Target size, confirming interactive controls meet the 24 by 24 pixel minimum, with 44 pixels preferred.
- Keyboard operation of the contact form, including the error summary, and of the video playback controls.
- Colour contrast, computed rather than judged by eye. Two accent colours are ruled out for body text on light backgrounds as a result.
Decisions this has forced
These are the real consequences, listed because they are more useful than a conformance badge:
- Links inside blocks of text carry underlines, because colour alone does not distinguish them at the contrast our palette allows.
- The hero and work sections remain readable with motion disabled. Videos load only when requested, with direct YouTube links available without JavaScript.
- Status and error messages use separate live regions, so progress is announced politely and a failure interrupts.
- Meaning never rests on colour by itself. Where a colour marks something, a word marks it too.
What has not been done
Automated testing finds a minority of real barriers. It is good at contrast, names, and structure, and it cannot tell whether a page makes sense when read aloud. So, plainly:
- There has been no full manual audit by a person who uses a screen reader daily. That is the gap that matters most, and it is planned rather than done.
- There has been no third-party certification or external audit.
- PDF documents linked from this site are not all tagged for assistive technology. Where one is not, the page says so rather than linking it silently.
- Content is in English only.
A conformance claim resting only on automated results would be worth very little, which is why the limits are on the same page as the claim.
If something does not work
Tell us and we will fix it. Accessibility problems are treated as defects, not enhancements, and they go to the front of the queue.
- Email [email protected]
- Phone 866-738-1020
- Or use the contact form
It helps to include the page, what you were trying to do, and the browser or assistive technology you were using. We review every accessibility message and reply directly.
Standards
The target is WCAG 2.2, opens in a new tab Level AA. Ontario's AODA website rules use WCAG 2.0 Level AA for organizations within their scope. Testing to 2.2 AA covers that earlier technical standard.