ACCESSIBILITY
Built to be usable.
What we build to, what we have actually checked, and what we have not. The last part is the part that matters, and it is dated.
How to read this
Written by the engineering team, and every claim below is limited to what has actually been checked. No third party has audited this product for accessibility, and the shelf-wide legal review does not cover it either. Last checked September 13, 2026. Where we cannot yet make a commitment, the document says so, dates it, and names what would close it. We would rather you found the gap here than found it yourself.
What would change that: An audit by somebody who does this for a living, and a test with people who use assistive technology every day. Until then, the section below is the whole of what we know rather than the whole of what is true.
What changed in this version: New document. There was no accessibility statement, and a product aimed at non-technical people as its primary audience owes one.
A printed copy carries this version and its date, and leaves the navigation behind.
What we build to
We aim at WCAG 2.2 level AA across every customer surface. That is a target we design and build against, not a certification we hold — nobody has audited this product against it and we will not imply otherwise.
- Every page works from the keyboard alone, in a visible order, with a skip link to the content and a focus outline you can actually see.
- Every page has one landmark structure and real headings, so a screen reader gets a map instead of a wall.
- Colour is never the only thing carrying a meaning; a state that matters has a word next to it.
- Text reflows to a phone and to a zoomed window without a horizontal scrollbar, and wide things — tables, code, diagrams — scroll inside their own frame instead of moving the page.
- Controls are at least 44 pixels tall, which is the size a thumb needs rather than the size a design wants.
- There is a Calm setting on every page that turns off motion, and it turns itself on automatically if your system asks for reduced motion.
- There is a Dawn theme for anyone who cannot read light text on dark, and it is a separately composed theme rather than an inversion.
- Nothing flashes, and nothing moves on its own except while something is genuinely happening.
What we have actually checked
Automated accessibility checks run against the built pages, and contrast is measured against the real compositing states of both themes rather than eyeballed. Keyboard order and focus behaviour are exercised on the pages that carry forms.
As of 2026-09-12 there has been no audit by a person who uses assistive technology daily, and no formal screen-reader testing pass across every surface. That is the honest gap and it is the one we would most like to close. If you use this product with assistive technology, telling us what breaks is worth more to us than any checklist.
If something is in your way
Write to us and say what you were trying to do and what stopped you. We answer within 10 working days, and an accessibility problem is treated as a defect rather than a request. If you need something in a different format in order to use the service, ask — that includes anything on the legal shelf.
Earlier versions
Every version this document has had. The one above is what you are reading now.
- Version 1.0 took effect September 12, 2026— current
We do not publish the superseded text, because a stack of old contracts on a public page is a way to be read out of context. The version you accepted stays retrievable: ask us naming the version and we will send you that exact text.
The rest of the shelf
- The deal in plain words
- Terms
- Privacy
- Data processing agreement
- Who can receive your data
- Cookies and storage
Questions about any of this reach a real person at the contact page, with or without an account — [email protected] for anything about your own data, [email protected] for a security report. We answer within 10 working days.