Accessibility statement

We want the site to be usable with a keyboard, a screen reader, a zoomed screen and a phone.

What we aim for

The Web Content Accessibility Guidelines (WCAG) 2.2, level AA. The pages, the windows (About) and the editors are checked automatically with axe in the light and the dark theme on every release, and by hand with the keyboard alone.

What is built for it

• Every control can be reached and used with the keyboard; the focus is always visible.
• Windows put the focus inside them when they open, close with Escape, and give it back.
• Changes that happen without a page load (a notice, an error) are announced to screen readers.
• Colours are chosen for contrast (4.5 to 1 for text), the colours of the two themes are both checked, and nothing is shown by colour alone.

What is not good yet

• The code editors are built on a library whose screen reader support is good for reading and limited for editing very large documents.
• The trees and the diff views carry a lot of structure; they are labelled, but a long document is long to move through.

Tell us about a barrier

If something does not work for you, use the contact form or write to [email protected], and say what you were trying to do and what you use. We will answer, and we fix what we can.