Accessibility
Everyone should be able to use a tool. Here's our commitment, and how to tell us if something gets in your way.
Last updated: June 16, 2026
The short version: toolcan targets WCAG 2.2 Level AA. Every tool works with a keyboard alone, has visible focus and labelled controls, and respects your reduced-motion and contrast preferences.
Our standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Accessibility is checked as part of building each tool, not bolted on afterwards, both with automated tests and manual keyboard and screen-reader passes.
What we build in
- Keyboard first, every control is reachable and operable with the keyboard, in a logical order, with a "skip to content" link as the first stop.
- Visible focus, a clear focus outline shows where you are at all times.
- Labelled controls, inputs, buttons, and the search box have proper labels and ARIA so screen readers announce them correctly.
- Live results, tool outputs use polite live regions so updates are announced without stealing focus.
- Reduced motion, animations honour your prefers-reduced-motion setting.
- Readable contrast, text and interactive elements meet AA contrast.
- No layout shift, ad and result areas reserve their space so content doesn't jump.
Known limitations
The site is built to AA, but accessibility is ongoing work and new tools ship regularly. Some third-party content (most notably advertising once it's enabled) is served by external providers and isn't fully under our control. If you hit a barrier, we want to know.
Tell us about a problem
If any part of toolcan is hard to use with assistive technology, please get in touch via the contact page and describe what happened, the tool or page, and the device or assistive technology you were using. We treat access barriers as bugs and aim to fix them quickly.
See also our disclaimer, privacy page, and terms.