NoaLingua for Chrome
Add to Chrome — Free Add to Chrome

Legal

Accessibility

This site targets WCAG 2.2 Level AA. Colour contrast has been audited programmatically in both themes and every text pair passes. Keyboard operation, semantic structure and reduced-motion support are built in. What has not yet happened is a full screen-reader pass.

The standard we target

WCAG 2.2 Level AA, for this website. Where we fall short we would rather say so here than let you discover it.

What has been done and verified

  • Colour contrast, audited programmatically in both themes. Every text and background pair clears 4.5:1, and the boundaries of interactive components clear 3:1. The audit found four genuine failures on its first run, which is why interactive borders use a separate colour token from decorative rules.
  • Meaning is never carried by colour alone. Every state in the coverage matrix has a shape and a text label as well as a colour, and comparison tables label the rows where a competitor wins rather than only tinting them.
  • Keyboard operation. Every interactive element is reachable and operable from the keyboard, with a visible focus ring. There is a skip link, and the mobile navigation and FAQ use native disclosure elements that work without JavaScript.
  • The site works entirely without JavaScript. The only script is the theme toggle; with it disabled, the site follows your system preference.
  • Semantic structure. One h1 per page, no skipped heading levels, real tables with headers and captions, and landmarks throughout. The build fails if a page breaks any of these.
  • Reduced motion. prefers-reduced-motion is honoured. There is no autoplay, no parallax, no scroll-jacking and no animated counters anywhere.
  • Reflow. Wide tables scroll inside their own containers, so the page itself never scrolls horizontally at 320px or at 200% zoom.

Known gaps

  • No full screen-reader pass yet. The markup is written for it and has been checked structurally, but it has not been driven end to end with NVDA, JAWS or VoiceOver. That is the largest outstanding item.
  • The coverage matrix is a large table. It is marked up correctly with row and column headers, but a 28-row, 10-column table is inherently demanding to navigate aurally. Per-language pages present the same data as a short three-column table, which is far easier, and that is the recommended route.
  • The extension itself is a separate question. This statement covers the website. Accessibility of the browser extension is not yet formally assessed.

What is stored and what can leave your device · what NoaLingua cannot do · every keyboard shortcut, and how to rebind them · contact

Reporting a problem

Email support@noasolutions.org. Tell us the page, what you were using, and what happened. Accessibility reports are treated as bugs rather than as feature requests, and they go to the front of the queue.