How we make our own work accessible
DraftDraft — these words are still waiting for Robin.
What we do to be accessible, what you can ask for, and what to do when we get it wrong.
We are led by disabled people, so we hold ourselves to what we ask of others. This page says what we do, what you can ask for, and what to do when we get it wrong.
Our website
- We build to Web Content Accessibility Guidelines (WCAG) 2.2 level AA. We test every page with a keyboard only and with a screen reader before it goes live. The test record is on the Sources page.
- Text can be made twice as large without anything breaking. Colours pass contrast in light and dark mode. Nothing flashes or moves on its own.
- We use words, not icons, for access information.
- Every page reads without JavaScript. Every form sends without it.
Our documents and events
- Everything we publish is available in large print, plain text, accessible PDF, and audio. The brochure is also in American Sign Language (ASL) video.
- Every event we run is in a step-free room with an accessible washroom, has a remote option, and has an ASL interpreter booked at least two weeks ahead. We use a relaxed format: come and go, move, make noise, take breaks.
- Ask for a format or an accommodation we do not list. We will try.
How to ask, and how fast we answer
- Email, text, phone, mail or video call — the details are on the Contact page. Formats are on the Formats page.
- We reply within five working days. If a format takes longer to make, we tell you the date within those five days.
- Formats are free.
When something is wrong
Tell us. Say which page or document, and what happened. We fix errors on the website within ten working days and write down what changed on the Sources page. If you are not satisfied, the Access Table hears feedback at every meeting; write "for the Table" in your message and it goes on the next agenda, with your name removed unless you ask otherwise.
What we cannot do
We cannot change other organisations' websites or buildings. We publish what we checked and tell them what we found.
Our test record
| Date | Tester | Tool and version | Result | Open items |
|---|---|---|---|---|
| September 21, 2026 | Automated checks | axe, pa11y, Lighthouse and a reading-level check axe-core 4.13.0, pa11y 9.1.1, Lighthouse 12.6.1 | On one first run the home page took 2.7 seconds to show, over our 2.5-second limit. Three more runs took about 2.2 seconds, so the limit is now judged on three runs. Every page asked for an icon file that does not exist; the site now says it has none. After that, every check passed: no errors on any public page in light or dark mode, every page at grade 8 or below, and accessibility 1.00 from Lighthouse on a phone. |
|
| September 18, 2026 | Automated checks | axe, pa11y and Lighthouse axe-core 4.13.0 | Every check passed. No errors on 29 public pages, in light or dark mode. Every page reads at grade 8 or below. The keyboard focus is always visible and follows the page. Nothing moves. Every button and link is at least 24 pixels. Pages still work at 200 % text size. pa11y found no problem on 25 pages. Lighthouse on a phone scored accessibility 1.00. |
|
| September 17, 2026 | Automated checks | axe axe-core 4.13.0 | Every check passed. No errors on 27 public pages, in light or dark mode. Every picture has a text description. Every page reads at grade 9 or below. The home, directory, report and rooms pages read in full without JavaScript and fit a narrow phone screen. The contact form sends without JavaScript. |
|
Last checked: September 24, 2026.