Accessibility

What we aim for

We build this site to meet WCAG 2.2 Level AA. In practice that means text that stays readable when you enlarge it, colour contrast that works for low vision, every part of the site reachable by keyboard alone, visible focus so you can see where you are, and headings and labels that make sense read aloud by a screen reader.

How we check

Every page is tested automatically for accessibility problems before it goes live, and we also work through the site by keyboard and with a screen reader by hand, because automatic checks miss things a person notices immediately.

What we have done

Every text colour on this site has been checked against both of the two background shades it can appear on, and each one meets the AA contrast standard on both. No status or meaning is signalled by colour alone — anything coloured also carries its own words.

The site can be operated entirely by keyboard. There is a skip link to the main content, every menu opens on focus and click as well as hover, Escape closes an open menu and returns you to the button that opened it, and closed menus are kept out of the tab order. Those behaviours are tested automatically in a real browser before each release rather than assumed from the code.

Every page is also checked at 360, 768 and 1280 pixels wide, and a page that scrolls sideways fails the build.

Where we fall short

We know of these, and we would rather list them than let you find them:

• Our downloadable books and presentations are PDFs that have not been checked for tagging or reading order. If one is hard to read with a screen reader, ask us and we will send you the text.
• This statement has not yet been reviewed by an accessibility specialist or tested with a person who uses a screen reader daily. Automatic checks and our own keyboard testing are not the same thing, and we would rather say so.
• We have no captions or transcripts for recorded teaching, because none of it is published on this site yet. Anything we do publish will carry them.