WCAG 2.2 accessibility audit

We check the site against all 55 WCAG 2.2 success criteria at levels A and AA. Each issue is pinned to its place on the screenshot and comes with a suggested fix. What cannot be settled automatically we do not guess — you get it separately, as a list for human review.

How we check

• Measurements on the rendered page — contrast of text and controls, target size, reflow at 320 px width, text spacing.
• Interaction — keyboard navigation and focus order, dialog behaviour, state changes of controls.
• An agent that reaches a goal with the keyboard only — like a person who does not use a mouse; on the way we check every state of the page that appears (menus, dialogs, messages).
• axe-core — a proven, embedded rule library, extended with our own checks.
• A language model — only where measurement is not enough, e.g. whether a link name describes its purpose or a heading describes its section.

We publish the results of our checks on the official W3C test cases (ACT Rules) together with the full report: Seerena WCAG Audit on the W3C tests.

European Accessibility Act

Since 28 June 2025 accessibility requirements apply to many products and services offered in the EU, including online shops, banking services, passenger transport, e-books and electronic communications. In practice the reference point for websites and apps is WCAG at level AA.

The audit helps you quickly see where a site falls short and decide the order of fixes. It is not a certificate or a legal opinion and does not confirm compliance — some criteria need human judgement, and whether a service is covered is decided by the law, not by a tool.

What you get

• A result for each criterion: failed, to verify, or no issues found.
• Issues pinned to the screenshot, with who they affect and a suggested fix.
• A list of items for human review — instead of guesses.
• The option to rerun the audit after fixes and compare.