Accessibility
We build and test the site for keyboard use, enlarged text, reduced motion and both colour themes. This page describes those checks and the gaps we know about.
Last updated
What we aim for
We build against the Web Content Accessibility Guidelines 2.2 at Level AA. That's the target we measure the site against. It isn't a certified result.
What we check
These checks run automatically each time the site changes. They cover each page we write ourselves and the first two pages of the resources listing. The resources section also republishes articles from another publisher. One of those is scanned with the automated rule checks each time, and every one of them has its heading structure checked when the site is built.
- Automated rule checks. Each page is scanned against the WCAG 2.2 A and AA rules an automated tool can test. A set of pages that between them use every colour on the site is scanned again in the dark theme.
- Keyboard use. Each page is walked from top to bottom using the Tab key alone. Each stop must be visible on screen and must show a focus outline. Where the header stays at the top of the screen, each page is also walked back up with Shift+Tab, and no stop may be hidden under the header. The "skip to main content" link has to move focus into the page content, and the navigation menus have to open, close on Escape, give focus back where it came from, and close when you tab out of them.
- Page structure. One first-level heading per page, no skipped heading levels, no empty headings, and a named main, header, footer and navigation region on each page.
- Resizing and reflow. Each page at a 320-pixel-wide screen, at 200% zoom, and with text size doubled. In each case there must be no sideways scrolling and no content cut off.
- Contrast. Text is measured against what's behind it on each page. Focus outlines and the borders of form fields are measured on the home and contact pages, including on the dark sections, in both colour themes.
- Reduced motion. With "reduce motion" enabled in your operating system, transitions, animation and smooth scrolling stop.
The site is built to need very little JavaScript. With scripting unavailable every page still reads and the menus still lead to every section. The contact form is the exception: its anti-spam check needs scripting, so without it an enquiry won't go through. Email us instead at the address below.
Where it falls short
These are the gaps we know about.
- No screen-reader testing. The checks above are automated. They can tell us a page is structured correctly, but not how it sounds. We haven't yet gone through the site with a screen reader.
- No independent audit. No one outside the company has reviewed this site for accessibility.
- Limits of automated checks. Automated tools can't find every accessibility problem. Testing by people is also needed.
- The anti-spam check on the contact page. That component belongs to Cloudflare, and we don't control what happens inside it. If it stops you sending an enquiry, email us instead. The address is below and it reaches the same place.
If something doesn't work
Email hello@praxbit.ca with the page you were on and what happened. We'll fix it. If you need information from the site in the meantime, we'll send it to you another way.
You don't have to use this website to deal with us. Anything here can be handled by email instead.
About this statement
It describes our own testing of this site, not an assessment by anyone else. If the testing or the known problems change, the date at the top of the page changes with them.