Accessibility of Accessa

Last updated: 25 October 2026

A tool that checks accessibility should be accessible itself. This page explains how the Accessa extension (version 1.3.0) and this website meet WCAG 2.2 level AA, how we checked it and what is not perfect yet.

Conformance status

Partially conformant with WCAG 2.2 level AA: nearly all content meets the criteria, with the exceptions listed below.

What we did

• Text contrast of at least 4.5:1 against the background, in both light and dark themes.
• Atkinson Hyperlegible Next typeface, designed by the Braille Institute for maximum legibility.
• All controls can be reached with the keyboard, and the focused element has a clearly visible yellow outline.
• Issue severity shown by shape and colour together (diamond, triangle, circle), not by colour alone.
• Buttons, switches and expandable sections built with native HTML elements, with names screen readers can understand.
• Interface in English and Italian, with the language declared in the code.

How we checked it

• Automated check with axe-core (the same engine Accessa uses) of the extension panel, the welcome page and every page of this website: no errors.
• Automated tests on every change to the extension, in a real browser, in English and Italian.
• We have not yet done a full manual review with screen readers: it is the next step.

Known limitations

• Highlights on the checked page. The coloured boxes Accessa draws on the page are a visual aid. Screen reader users find the same information (issue, element, code) in the extension panel.
• Element code. The code excerpt shown for each element is technical HTML and can be long to listen to with a screen reader.
• No testing with disabled users has been done yet. We would like to: if you use assistive technology and want to help, please get in touch.

Report a problem

If you find a barrier in the extension or on this website, write to accessa.eaa@gmail.com with the page and what does not work. We reply within 5 working days.