Everybody has to be able to use it

What we build to

The Web Content Accessibility Guidelines 2.2, level AA. That covers semantic markup and correct heading structure, forms that announce their own errors, everything reachable and operable by keyboard alone, visible focus, colour contrast that meets the standard, targets big enough to hit, and layouts that survive text being scaled or the page being zoomed.

It is checked as the work is done rather than audited afterwards. The design system carries the rules — a component cannot be built with a colour that fails contrast, because the token that would fail is not offered.

Including the emails, which is the part usually missed

An invitation, a password reset and a certificate notice are as much a part of the product as any screen, and they are where accessibility work normally stops. Ours carry the language of the message, structural markup that survives a mail client stripping the styling, a text alternative for every image, and a plain-text version that says what the HTML says rather than what the markup implies.

A tenant's brand colours are contrast-checked before they are used. A bright accent that would be unreadable as a link is darkened until it passes rather than being silently swapped for ours — so a reseller keeps their brand and their learners keep a message they can read.

What is not there yet

Being specific about this is the point of publishing a statement at all.

Some parts of the administration console — the course editor and the navigation builder in particular — are designed for a large screen and are not usable on a phone. Rather than present a broken version, they say so and point to a desktop.

We have not commissioned a third-party audit. When we do, we will publish it here, including the parts we fail.

If you use assistive technology and something does not work, that is the most useful information we can get, and we would rather have it as a sentence in an email than not at all.

Telling us

Write to us through the contact page and say what you were trying to do, what happened, and what you were using. You do not need to know the standard or name the failure — describing it in your own words is enough.

There is also a "Trouble signing in?" control on the sign-in screen itself, for the case where somebody cannot get far enough into the platform to report anything.

We will tell you what we are going to do and when, and we will come back to you when it is done.