Skip to content

Accessibility Statement

What we do to keep every tool usable with a keyboard, a screen reader or low vision — including the parts that are not there yet.

Last updated 9 September 2026 WCAG 2.1 AA target

Our aim

A tool that only works if you can see it and use a mouse is not finished. ToolQivo aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, and to be usable with the assistive technology people actually run: screen readers, keyboard-only navigation, magnification and voice control.

This statement describes the current state honestly, including where we fall short. It is not a certification.

What is in place

  • Keyboard access. Every control — menus, tool inputs, copy and download buttons, the search box and its suggestions — can be reached and operated with Tab, Enter, Space and the arrow keys. Focus is visible rather than styled away.
  • Real semantics. Pages use proper headings in order, real buttons and links, labelled form fields, and landmark regions, so a screen reader can describe the page and skip through it.
  • Labels on everything. Icon-only controls carry accessible names, and inputs are tied to visible labels rather than relying on placeholder text.
  • Contrast. Body text, headings and interface text are chosen to meet the 4.5:1 contrast ratio, and interface components the 3:1 ratio, against their backgrounds.
  • Zoom and reflow. Layouts are fluid, so the site can be zoomed to 200% or viewed on a narrow screen without content being cut off or requiring horizontal scrolling.
  • Status messages. Results, errors and confirmations are announced rather than only appearing visually.
  • No motion traps. Nothing auto-plays with sound, nothing flashes, and animation is decorative only.
  • Speed as accessibility. Pages are light and load quickly, which matters on an old device or a slow connection.

Known limitations

Some things are genuinely hard, and it is more useful to name them than to claim full conformance:

  • A few tools are visual by nature — colour pickers, gradient builders, image croppers. We provide numeric entry alongside the visual control wherever we can, but the visual result itself cannot be conveyed to a screen reader.
  • Advertising is supplied by a third party. Its markup, contrast and behaviour are outside our control, and it is the most likely source of an accessibility problem on any page.
  • A handful of older tool pages have not yet been through the same keyboard and screen-reader pass as the newer ones. They are being worked through, oldest first.
  • Complex tables of results are readable but can be tedious to navigate cell by cell.

How we test

New and changed pages are checked by navigating them with the keyboard alone, by running an automated audit for contrast, labelling and structure, and by listening to the page in a screen reader. Automated checks catch perhaps half of what matters, so the manual passes are the ones that count.

Tell us when we get it wrong

If you hit a barrier on this site, please report it — it will be treated as a bug, not a suggestion. Write to toolqivo@gmail.com with "Accessibility" in the subject line, or use the contact form, and include:

  • the page URL;
  • what you were trying to do and what stopped you;
  • the assistive technology, browser and operating system you were using.

We aim to reply within 2 working days and to say what we intend to do about it. If something cannot be fixed quickly, we will tell you that as well, and describe another way to get the same job done.