Last updated: 24 October 2026

AtoZTools is a working tools site, and tools are only useful if everyone can operate them. We aim for this site to meet the WCAG 2.2 AA standard, and accessibility checks are part of the checklist a tool must pass before it is published — including that the tool works with a keyboard alone.

What is built in

  • Skip link. Every page starts with a "Skip to main content" link, the first thing a keyboard or screen-reader user meets.
  • Visible focus. Interactive elements get a clear focus outline (a :focus-visible style), so you can always see where you are when moving by keyboard.
  • Announced results. Tool status lines and result areas use aria-live regions, and form outcomes use role="status" or role="alert", so progress, success and errors are announced to screen readers rather than shown only on screen.
  • Labelled controls. Every form field has a visible text label connected to it; buttons and icon-only controls carry accessible names.
  • Keyboard operation. Tools are built from native buttons, inputs and links, menus close with the Escape key, and frequently asked questions use native <details> elements that open and close from the keyboard without scripting.
  • Not colour alone. Status and severity are always given as text labels alongside colour, never by colour only.
  • Motion. The site honours the prefers-reduced-motion setting and reduces animation for visitors who ask their system for that.
  • Contrast and text. The design system's text and background colours are chosen to meet WCAG AA contrast ratios, body text is set at a readable size, and pages work at high zoom without horizontal scrolling of the main content.

Known limitations

We would rather name these than over-claim:

  • No screen-reader lab testing yet. Our checks so far are code review, keyboard testing and automated checks. We have not yet completed formal testing sessions with a range of screen readers and assistive technologies, so barriers may exist that our current checks have not caught. Reports from assistive-technology users are the fastest way for us to find them.
  • Visual results. Some tools present results visually by nature: charts are drawn on a canvas, and the image and PDF tools show previews and page thumbnails. The numbers and files behind those visuals stay available in the tools' data and download views, but the visual itself cannot carry the same information for everyone.
  • Complex outputs. Dense outputs such as tree views and side-by-side comparisons are harder work with assistive technology than simple forms, even with headings and live regions in place.
  • Content we fetch. The checker tools report on other people's websites. We present those reports accessibly, but the accessibility of the sites being checked is outside our control.

Tell us about a barrier

If any part of this site is hard or impossible for you to use, please tell us via the contact page or at contact@atoztools.pro. It helps to name the page, what you were trying to do, and — if you are comfortable sharing it — the assistive technology and browser you use. Accessibility reports are treated as bugs: they go into the same fix queue as a broken tool, and we will reply to let you know what we found.