Skip to content
Attesta
Current language: ENNederlands: NLDeutsch: DEFrançais: FREspañol: ES
Log inScan your site

Accessibility statement

Last reviewed: 19 July 2026 · Next review: by 19 January 2027 or on any major release

We build a tool that measures websites against the accessibility standards the European Accessibility Act points to. It would be indefensible to hold our customers to a bar we don't meet ourselves — so we audit Attesta against the same standard, publish what we find, and fix it in the open. This page is the honest version: what conforms, what doesn't yet, and how to tell us when we've got it wrong.

What we aim for

Attesta — both the public marketing site and the signed-in dashboard — targets WCAG 2.1 level AA and EN 301 549, with the WCAG 2.2 AA additions applied where practical. We describe our status as substantially conformant: the great majority of the standard is met, with the specific, documented exceptions listed under Known limitations below. We do not claim a formal third-party certification, and — as everywhere in Attesta — we never present a score as a legal guarantee of conformance.

What we've done

In July 2026 we ran a full self-audit across every page of both surfaces. It combined our own scanner and axe-core (automated) with a manual pass for the things tools cannot judge: keyboard-only operation, screen-reader output, 200 % zoom and 400 % reflow, reduced-motion, colour independence, contrast, form labelling and error handling, heading and landmark structure, and page titles. The full findings and their resolutions live in our audit record.

The audit found — and we fixed — a systemic contrast shortfall (some primary buttons and links sat just under the 4.5:1 minimum), a missing "skip to content" link, a missing main-content landmark on some pages, generic page titles on the app screens, and a gap where a screen reader was not told when a scan finished. To keep these from returning, three checks now run in our continuous integration on every change: automated axe checks on every key route (the build fails on any new critical or serious issue), a lint rule that forbids removing a focus outline without providing a visible replacement, and a test that our severity indicators always render an icon and a text label, never colour alone.

Known limitations

We'd rather name these than hide them. As of the last review, we are aware of the following, none of which block a core task; each has a planned fix:

  • Stacked tables on small screens. On narrow viewports and at very high zoom, some data tables collapse to a card layout in which the column headers are not programmatically tied to each cell. The same information is available in the report and monitoring views; a per-cell header fix is planned.
  • Account menu keyboard model. The account menu opens, closes on Escape, and every item is reachable by Tab, but it does not yet implement arrow-key roving focus.
  • Score-over-time chart. The trend chart exposes a summary to assistive technology; the exact point values are available in the adjacent scan-log table rather than inside the chart itself.
  • Exported PDF reports. The PDF export is readable, but we have not yet independently verified it against PDF/UA (tagging, reading order, image alternatives). Until we have, treat the on-screen report as the accessible source of record.
  • Screen-reader coverage. We test with the keyboard and with automated tooling on every release; full manual screen-reader verification across NVDA, VoiceOver and JAWS is ongoing rather than complete.

Compatibility

Attesta is built to work with recent versions of Chrome, Edge, Firefox and Safari, with the browser's own zoom and with assistive technologies that support those browsers. It does not require JavaScript to read the marketing content, and it respects your operating-system "reduce motion" setting.

Tell us about a barrier

If any part of Attesta gets in your way, we want to hear about it — it's the fastest way we improve, and we treat these reports as a priority. Please tell us the page, what you were trying to do, and the browser or assistive technology you were using.

If you contact us about a barrier and aren't satisfied with our response, you can raise the matter with the accessibility enforcement body in your EU member state under the European Accessibility Act.

How this statement was prepared

This statement reflects a self-assessment carried out by Attesta in July 2026, combining automated testing (our own scanner and axe-core, now part of our continuous integration) with manual evaluation. We review it on every major release and at least twice a year.