Accessibility
If you cannot use this, that is our problem to fix.
People come to this product under stress, often on an old phone, sometimes with a disability, usually against a deadline. Any one of those makes a badly built page unusable. Here is what we check, and what we have not done yet.
What we check on every screen
- Contrast is measured, not eyeballed
- We measure the contrast of every text color against its background. Text meets the WCAG AA level of 4.5:1, and large text 3:1. We measure the colors the browser actually draws, not the ones we picked in the design.
- The page works at small widths
- We check every screen at 320, 375, 768 and 1280 pixels wide, and nothing scrolls sideways. The smallest size is an older phone. That is what many people are holding when they read a court notice.
- Headings describe the page
- Each page has one main heading, and headings never skip a level. That way people using a screen reader or a keyboard can jump around a page instead of reading all of it.
- Keyboard focus is visible
- Buttons and links show a clear outline when you move to them with a keyboard. Pictures that are only decoration are hidden from screen readers, so nothing is read out twice.
- Motion respects your settings
- If your device asks for reduced motion, animations are turned off rather than shortened.
What we have not done
We do not claim formal WCAG conformance, because nobody has audited this and we are not going to assert something we have not verified. Specifically:
- No independent accessibility audit has been carried out.
- We have not tested with screen readers, voice control, or switch access on real devices.
- Parts of the product are still being built. Newer screens have had less scrutiny than older ones.
Telling us something is broken
If any part of this site stops you doing something, send us a message. Tell us the page and what happened, and what you were using if you know it. A report about a screen you could not get past is treated as a bug in the product, not a support question.