Your shortlist:

Built for everyone

Accessibility

The standard this site is built to, how I test it, what I know still falls short, and exactly what to do if something gets in your way.

Last updated

A website some people can't use isn't finished. That goes for this one first.

01 The standard I build to

Kootenay Helpers is built to WCAG 2.2 AA, the Web Content Accessibility Guidelines published by the W3C, the same standard as every site that leaves my desk. It is how the pages are made, from the first template.

For public bodies in British Columbia, the Accessible British Columbia Act sets accessibility obligations, and public-sector work commonly names WCAG 2.1 AA as the floor. Building to 2.2 AA covers that and goes further, because 2.2 includes everything 2.1 asks for and adds newer criteria on top.

02 What that means here

Structure

Every page has one heading at the top, headings in order, landmarks, lists that are lists and buttons that are buttons. The first thing your keyboard reaches on every page is a link that skips to the main content.

The week grid

“Want a set day and time?” opens a real table. Each cell's name to a screen reader is its day, its part of the day and its count, for example “Saturday morning, 11 roles”. The grid is one tab stop: arrow keys move between times, Space picks one, and a polite announcement reads the new count. A hint beside the grid says so.

Without JavaScript

Every list, filter and town picker is a plain link or a form, so the site works with scripts off. The grid becomes checkboxes and a button.

Keyboard

Everything interactive can be reached and used with a keyboard alone, with a visible focus ring so you always know where you are.

Contrast and type

Every text and background colour pair on the site clears the AA contrast floor, measured on the rendered page. The prints behind some sections use colours from those same measured pairs. Layouts hold at 320 pixels wide and at 200 percent text size, and the grid steps down to fit.

High contrast and dark modes

The site declares one colour scheme and keeps it under forced dark mode. In Windows High Contrast every grid cell, button and link keeps a visible boundary.

Tap targets

Grid cells are 44 pixels square on phones 390 pixels wide and up, 40 on narrower phones and 38 at 320 pixels. Every button and link is at least 24 pixels tall with room around it, so a near miss on a phone lands nowhere.

Motion

Motion here is small and short. The painted figures step forward, rise onto their waterline and walk out with a note, and quilt patches settle in and lift when you reach them. Nothing loops. Turn on “reduce motion” in your device's settings and each one is simply there, with nothing in motion.

Images

The illustrations carry alt text where they say something and are marked decorative where they do not, and so are the landscapes and prints. No image carries words.

Measurement

Before a page goes live, automated checks run on it at phone and desktop sizes. They test the WCAG 2.2 AA rules, the colour contrast, the size of every button and link, and the order the keyboard moves through the page. They take pictures of each page in dark mode, the browser's forced dark mode, high contrast colours, big text and reduced motion. They also check that every number on screen matches what its link opens. Then I check by hand, with a keyboard and with the page zoomed in. Automated tools catch only part of the problem, so passing them is only the start.

03 Where this site stands

I hold this site to the standard I sell. It is new and changes often, so if something falls short I want to know, and I will fix it rather than argue about it. These are the limits I know about today.

Pages for expired links

When a link in an email has run out, the page that says so is drawn by the browser after the page loads. With scripts off you see a blank page and a 404 status. The fix is on my list.

Safari on iPhone

My automated checks run in a Chromium browser and in WebKit, the engine behind Safari, at phone size. That isn't the same as a real iPhone, so if Safari does something odd, tell me.

Screen readers

Automated checks read the page's structure and the names of its controls, and I check it with a keyboard. A full pass with a real screen reader across every page is still to come.

Other groups' pages

The details of a role and the way to apply live on each group's own website. I cannot fix those pages, but if one blocks you, tell me and I will find another way to get you in touch with the group.

04 Found a barrier? Tell me

If any part of this site is hard to use with assistive technology, or hard to use at all, email me at hello@kootenayhelpers.ca, or call or text 778 761 5897. Tell me what happened and what you were using. I read every message myself and I reply within 24 hours.

Every report gets the same treatment: I fix it first, then check the fix with the same kind of setup that hit the problem, and then I write back to tell you what changed. Anyone who takes the time to report a barrier is doing me a favour.

05 Who keeps this

Kootenay Helpers is built and kept by Kootenay Made Digital in Castlegar, BC, and the same standard applies to every site the studio makes. If you run a community group and want your own site to meet it, the studio's accessibility page explains how that work is done.