Accessibility
LAST UPDATED 12 SEPTEMBER 2026
We aim at WCAG 2.1 Level AA. The marketing pages have been tested against it and pass the checks listed below. The signed-in application has not been fully audited yet, and we would rather say so than imply otherwise.
Target
We aim to meet WCAG 2.1 Level AA. This statement records what has been measured rather than what we intend, and is updated when either changes.
What has been verified
Automated and manual checks run against the production build of the public pages:
| Check | Result |
|---|---|
| Heading structure | One h1 per page, no skipped levels |
| Landmarks | header, main and footer present; page language declared |
| Images and icons | No unlabelled graphics; decorative marks hidden from assistive technology |
| Text contrast | Body text 18.9:1, muted text 5.1:1, accent 4.6:1 — all at or above AA |
| Colour independence | Struck-out words use a real <s> element, so the meaning survives without colour |
| Keyboard | Every control reachable in a logical order with a visible focus ring; no traps |
| Reduced motion | prefers-reduced-motion is honoured; all content renders in its final state |
| Without JavaScript | Pages remain fully readable |
| Zoom and reflow | Readable at 200% and at 320px wide without horizontal scrolling |
What has not been verified yet
Stated plainly, because an accessibility statement that lists only successes is marketing:
- The signed-in application has not had a full audit. The dashboard, the post editor and the settings screens have had no formal conformance review.
- The rich-text editor is a known weak point. It is built on a third-party component whose keyboard and screen-reader behaviour we have not independently tested. If you rely on a screen reader to write, contact us before subscribing and we will tell you honestly whether it will work for you.
- Charts on the analytics pages convey information visually and do not yet have equivalent text alternatives.
- No testing with real assistive-technology users. Automated checks and keyboard testing catch a great deal, but they are not a substitute for this, and we have not done it.
- No video content exists, so captions are not currently applicable. If we add video, it will ship with captions.
Tell us if something does not work
Email support@example.invalid with the page and what went wrong. We aim to reply within five working days. If a barrier stops you using something you have paid for, we will fix it or refund you.
How this was tested
Automated structural and contrast checks run against the production build, plus manual keyboard traversal, reduced-motion emulation and a JavaScript-disabled pass, on a recent Chromium build in September 2026. Contrast ratios are computed from the source colour tokens and asserted in our automated test suite, so they cannot drift unnoticed.