Accessibility

Our commitment

We aim for this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which includes everything in WCAG 2.1 AA. Those guidelines explain how to make web content easier to use for people with disabilities, and for everyone else too.

If something on the site gets in your way, we treat it as a bug and want to hear about it.

What we do

• Semantic HTML. Pages use real headings in order, landmarks (header, navigation, main content, footer) and lists, so screen readers can move around them. A “Skip to content” link is the first thing on every page.
• Keyboard navigation. Every link, button and form field can be reached and used with a keyboard alone, including the mobile menu.
• Visible focus. The element that has keyboard focus is always marked with a clear copper outline or ring.
• Color contrast. We checked our text, button, form field and focus colors against the WCAG AA contrast ratios, and we don’t use color alone to carry meaning.
• Zoom, text size and spacing. Pages work at up to 400% zoom and on screens as narrow as 320 pixels without scrolling sideways. Wide tables, and the home page’s four steps on narrow screens, scroll sideways inside their own box instead, and you can scroll them with the arrow keys. Pages keep working if you make text larger or increase line, letter or word spacing.
• Reduced motion. The site uses very little animation, and it turns animation and smooth scrolling off when your device is set to reduce motion.
• Text alternatives. Images that carry information have alt text. Purely decorative images are hidden from screen readers.
• Forms. Every form field has a visible label, and optional fields say so. If something needs fixing, the error is shown in text next to the field and linked to it, and focus moves to the first field that needs attention, so screen readers read it out. The result of sending a form is announced too.

How we test

We last reviewed the whole site on September 23, 2026. For every page, we:

• run two automated checkers, axe and HTML_CodeSniffer, against WCAG 2.2 level AA;
• use it with a keyboard alone, checking that focus is always visible and never hidden behind the page header;
• check it at a width of 320 pixels (the same as 400% zoom), with larger text spacing, in Windows High Contrast mode and with reduced motion;
• check text and control colors against the WCAG contrast ratios.

We also fill in the contact form with a keyboard alone, including its error messages and the checkbox it shows when the spam check can’t confirm you’re a person. We run these checks again whenever we change the site.

Known limitations

We know about these and are working within them:

• App screenshots. Pictures of the Toolix app on this site are illustrative images, not live text. Each one has a text alternative that describes what it shows, but the words inside the screenshot can’t be selected or resized like page text.
• Spam check on the contact form. Our contact form (which also takes deletion requests) uses Vercel BotID, an invisible check that needs nothing from you. If it can’t confirm you’re a person, the form shows a single checkbox. Ticking it runs a short automatic check: there are no puzzles, images or audio to solve. If it still doesn’t work, try another browser or device. Account deletion is also always available in the app under Settings → Delete My Account.

The Toolix app

The Toolix app for iPhone and Android is built with standard controls, and most of its text grows with your device’s text size setting. Screen readers (VoiceOver on iPhone, TalkBack on Android) read most buttons and lists by their visible text, but some buttons that show only an icon don’t have a spoken name yet. We’re working through those. If a screen in the app doesn’t work with your setup, tell us which screen it is and which setting or assistive technology you use, and we will look into it.

Report a barrier

If you have trouble using any part of the website or the app, tell us through the contact form and choose “Accessibility problem with the site or app”. It helps if you tell us:

• the page address or the app screen where you had the problem
• what you were trying to do and what happened instead
• your device, browser or app version, and any assistive technology you use

A real person reads every report and replies by email, usually within two business days. Where we can’t fix the problem straight away, we will get you the information or help you need another way. If you need any page on this site, including our privacy policy or terms of service, in a different format, ask through the contact form and we will send it to you.