Our commitment
We believe a software shop should be usable by everyone — keyboard-only users, screen-reader users, people with low vision, people with motor differences, people on small phones in poor light. We design and build to WCAG 2.1 Level AA as the minimum bar and treat any failure to meet it as a bug to fix, not a feature to defer.
This statement covers every page on the site. If something does not work for you with the assistive technology you use, that is on us — please tell us so we can fix it.
What we do for accessibility
Specifically, the engineering team holds itself to:
- Keyboard navigation — every interactive element is reachable with Tab, activatable with Enter or Space, and dismissable with Escape. We do not use mouse-only patterns.
- Semantic HTML — landmarks (`<main>`, `<nav>`, `<footer>`), headings in correct order, native form controls, real buttons. Screen readers should never need ARIA to make sense of a page they could understand from the markup alone.
- Visible focus — every interactive element shows a focus ring at all times when focused via keyboard, with at least 3:1 contrast against its background.
- Colour contrast — body text at 4.5:1, large text and icons at 3:1, in both light and dark modes.
- Resizable text — pages remain usable up to 200% zoom in any browser; no fixed-pixel content widths block reflow.
- Reduced motion — animations respect `prefers-reduced-motion` and never autoplay video with sound.
Keyboard shortcuts
Standard browser shortcuts work everywhere. The site adds two of its own:
- / — open the search palette from any page.
- Escape — close any dialog, drawer or menu.
We deliberately keep the shortcut list tiny so it does not collide with assistive-technology key bindings.
Browsers and assistive tech
We test on the latest two versions of Chrome, Edge, Firefox and Safari on desktop, and Safari and Chrome on iOS and Android. We test screen-reader behaviour with NVDA + Firefox, JAWS + Chrome, VoiceOver + Safari (macOS and iOS), and TalkBack + Chrome on Android.
We do not test against Internet Explorer 11; it is no longer supported by Microsoft and we do not block it but cannot guarantee accessibility there.
Known issues
We track open accessibility issues in the same backlog as functional bugs and treat them with the same priority. The current short list:
- The interactive product comparison table on `/compare` does not yet announce row updates to screen readers when filters change. Workaround: re-load the page to hear the updated rows. We expect to ship a fix in the next release cycle.
- Some marketing video embeds rely on third-party players whose captions we cannot verify. We are migrating to self-hosted captioned players.
If you hit something not on this list, please tell us — see the next section.
Reporting an accessibility issue
If a page does not work for you with your assistive technology, write to us via the contact page and tell us what you tried, what happened, and what should have happened. We aim to respond within two business days and to confirm a fix or workaround within ten.
This page is reviewed at least once a year and after any major release.