Everyone should be able to use what we build
Accessibility isn’t a checkbox for us — it’s part of building software people actually rely on. Here’s what’s built in today, the standard we hold ourselves to, and how to tell us when we fall short.
Last reviewed: September 12, 2026.
Adjust this site to suit you
Look for the ♿ Accessibility button in the bottom-left corner of every page. It opens a small panel where you can turn on larger text, a more readable font, always-underlined links, and reduced motion. Your choices are saved on your device — no account needed — and apply everywhere on the site.
Built-in preferences
The on-page widget lets anyone scale up text, switch to a highly-legible font, underline every link, and calm animations — instantly, with no downloads or sign-in. Settings persist across visits on the same device.
Keyboard-friendly
The site is built for keyboard use: every page opens with a “Skip to main content” link, interactive controls are reachable and operable without a mouse, and focus is made visible so you can see where you are (more so with the widget’s focus-outline option on). We verify this on our main pages, and we’re steadily working through the rest — if you hit a spot that traps or loses keyboard focus, please tell us.
Works with screen readers
We use semantic HTML, meaningful landmarks, descriptive link text, and alternative text on images, so assistive technology can present pages sensibly. Interactive controls carry accessible names and states.
Respects your system settings
If your operating system or browser is set to reduce motion, we honour it automatically. The manual “reduce motion” toggle is there for when you want it on just for this site.
Readable by default
We aim for comfortable line length, generous spacing, and sufficient colour contrast in our core palette — before anyone touches a setting. The widget goes further for readers who need it.
How we test
As we build, we check pages with keyboard-only navigation, browser zoom to 200%, a reduced-motion setting, and automated structural checks (one <h1> per page, logical headings, landmarks, image alt text, and colour contrast in our core palette), plus a screen reader where feasible. This is honest self-assessment by a small team — not a third-party audit — and coverage across every page and flow isn’t yet exhaustive.
The standard we aim for
We work toward the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We’d rather be precise than impressive: we’re a small studio, this is a genuine work in progress, and we won’t claim a certification we haven’t earned. What’s described above is what we actually do today.
If your procurement process needs an accessibility conformance report (an ACR / VPAT) or has specific Section 508, ADA, or state requirements, get in touch — we’re glad to work through it with your team.
Known limitations we’re working on
We’d rather name specifics than say “some areas.” As of the review date above:
- The wide product-comparison table on the Solutions page is dense on very small screens; a clearer narrow-screen presentation and a plain-text summary are in progress.
- A few animated or live elements (the homepage counters and the live-API status readout) are checked for keyboard use and reduced motion, but not yet with every screen-reader and browser combination.
- Our on-page accessibility widget and the cookie-consent banner are recent additions; we’re still refining their screen-reader wording and focus behaviour.
- Coverage of our full WCAG target is not complete page-by-page — our primary marketing pages get a closer check than some legal and blog pages.
If you rely on something not listed here and it isn’t working, that report is exactly what helps us most — see below.
Hit a barrier? Tell us.
If something on this site was hard or impossible to use, we want to know — it’s the fastest way we improve. Please include the page, your device, and any assistive technology you were using.