Reporters can now speak their report. Voice reporting is live on all plans.Learn more

WCAG 2.2 AA · EN 301 549

Accessible whistleblowing: WCAG 2.2 AA for the reporting channel

A reporting channel that a keyboard user, a screen reader user or someone on a 320-pixel screen cannot complete is a channel that fails the people it exists for. Here is what accessibility means for a whistleblowing form, and what Ashio does about it.

Last reviewed: November 1, 2026

Definition

What does WCAG 2.2 AA mean for a report form?

WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, and the version EN 301 549 has carried in full since September 2026. Level AA is what public-sector procurement in Europe asks for. For a whistleblowing form it comes down to four promises: the form can be completed with the keyboard alone, every field has a name a screen reader can announce, problems are described in text rather than with colour, and the layout still works at 200% zoom.

Requirements

The criteria that decide whether someone can file a report

Not the whole guideline, only the parts that stand between a reporter and a submitted report.

Labels and instructions (1.3.1, 3.3.2)

Every field has a label a screen reader can announce, and a rule such as a minimum length is stated next to the field instead of being discovered on submit.

Keyboard only (2.1.1)

The wizard can be finished without a mouse. Moving to the next step takes focus with it, so the fields that just appeared are not skipped by the next Tab.

Visible focus (2.4.7, 2.4.11)

The focused control is outlined at 3:1 contrast, using an outline rather than a shadow, so it stays visible in Windows High Contrast.

Error identification (3.3.1)

A rejected field is named in text and the browser message appears on the field itself, not in a banner somewhere above it.

Contrast (1.4.3, 1.4.11)

Body text at 4.5:1, field borders and icons at 3:1, and placeholder text treated as text because it is text.

Screen reader support (4.1.2)

The anonymity choice is one group with a legend, progress is announced as a position in a list, and the voice recorder speaks its state when it changes.

Those six are not a wish list: they are how the Ashio report form behaves. Fields are labelled, the step change moves focus, errors come from the browser itself, and nothing depends on colour. What we do not offer is a WCAG badge, because no one can issue one.

Why it matters

Accessibility is a requirement, not a courtesy

Public-sector bodies in the EU have had to meet EN 301 549 for years, and since 28 June 2025 the European Accessibility Act extends comparable duties to many private services. The channel is usually bought by the same people who run that programme, and conformance is increasingly a line in the tender.

  • Procurement: EN 301 549 is cited by name, and an accessibility conformance report is expected with the bid.
  • Employees: a channel that cannot be completed by keyboard or screen reader silences the people least able to complain elsewhere.
  • Reporting duty: the Directive protects the reporter, so a barrier in the channel undermines the protection it is meant to provide.

FAQ

Frequently asked questions

Is there such a thing as WCAG certification?+

No. WCAG has no certifying body, so nobody can hold a WCAG certificate. What exists is a declaration: the vendor states the conformance level, the screens and flows it covers, and how it was tested. Public-sector sites in the EU must also publish an accessibility statement. Ask for the scope and the method, not for a badge.

What is EN 301 549?+

The European harmonised standard for accessible ICT procurement. Version 4.1.1, published in September 2026, carries WCAG 2.2 AA in full, alongside requirements WCAG has no equivalent for: documents, hardware, support services. That is why public tenders cite the standard rather than the guideline.

Does WCAG apply to an internal tool?+

It applies to staff as users, not only to the public. Equality law in most member states already covers employment tools, the same standard reaches services covered by the European Accessibility Act, and if you are a public body the channel is part of what your accessibility statement has to cover. The report form is also the one internal form somebody may have to complete at the worst moment of their working life.

What is harder about a whistleblowing form than a normal one?+

Four things. The person filling it in is usually there once, under stress, and may be afraid of being identified, so the anonymity choice has to be clear on the first reading. The form runs in steps, so every step change has to move focus or the next Tab skips the fields that just appeared. It has a voice recorder, which has to say what it is doing. And the submission is encrypted in the browser, which must never leave someone stuck on a disabled button with no explanation.

How do we test whether our channel is accessible?+

Four passes, none of them needing a tool: file a report using only Tab, Shift-Tab, Enter and the arrow keys; file one with a screen reader running and the monitor off; zoom to 200% and shrink the window to 320 pixels and check nothing disappears; and submit an empty step to see whether the error is announced. A whistleblowing form fails most often at the step change, not at the fields.

Do we need Level AA or Level AAA?+

AA. It is what EN 301 549, the European Accessibility Act and Section 508 all point at, and what a tender's criteria mean in practice. AAA is a higher bar that no public procurement asks for and that a single form cannot promise in full.

EU directives covered

Related compliance guides.

Explore Ashio's coverage of each EU regulation.

An accessible channel, from the first report

Start a free 14-day trial, publish your report page, and complete a test report with the keyboard alone.