Documentation
Everything you need to run accessibility audits, interpret results and integrate Axively into your workflow.
Sections
Getting started
Run your first scan, understand the report, fix your first issue.
WCAG 2.2 AA
How Axively maps violations to WCAG success criteria. What we detect, what we don't.
EN 301 549
The European harmonised standard for ICT accessibility. What it adds on top of WCAG.
Per-country legal mapping
How we calculate exposure per country. Sources, enforcement authorities, penalty ranges.
Compliance statements
Generate and publish accessibility statements in the correct format for 27 EU member states.
Technical support
Couldn't find an answer? Write to support@axively.com, we usually reply within 24 hours on business days.
Methodology
How the scanner works
Axively visits your site in a real browser (Chromium via Playwright), the same way a visitor sees it, including JavaScript and dynamic content. On each page, after it has fully loaded, it runs the axe-core testing engine. We crawl considerately (a delay between pages) up to a depth of 2 levels and up to 1,000 pages per audit. Because audits are run by site owners on their own sites, we identify ourselves with the Axively user agent and do not enforce robots.txt during an audit; owners who do not want their site audited can contact us.
What exactly we test
We use axe-core, the industry-standard accessibility testing engine (the same engine powers Google Lighthouse and Microsoft Accessibility Insights), with the rule sets wcag21aa (WCAG 2.1 levels A and AA), wcag22aa (WCAG 2.2 additions at AA) and best-practice (axe best practices beyond WCAG). For the European context we map findings to EN 301 549, specifically clause 9 (web content). Clauses 11 (software) and 12 (documentation and support) are not covered by an automated scan and require manual assessment.
How the AI fix suggestions are made
Each unique type of finding is passed through a modern language model that generates a plain-language explanation of the impact and a concrete code fix based on your site's actual HTML. Suggestions are translated into your account's language. Key principles: the AI suggests, it does not apply, changes to your code are made by your developer after review; suggestions are generated from the real element context, not from generic templates; and identical problems share one suggestion (which is why audits stay fast and cheap even on large sites).
Security and data
Audit data is stored in the EU, on a single dedicated server in the Czech Republic (provider Huko.net). We scan only the publicly accessible content of your site; the results are visible only to your account. For data processors and retention, see our privacy policy.
How to read the report
A violation is a single occurrence; a rule is the underlying cause, one problem in a template produces many occurrences, so always fix by template and component first. Findings are ranked by severity with recommended timeframes: critical within 7 days, serious within 30, moderate in your normal development cycle. When the fixes are deployed, run the free verification re-scan to confirm a clean before and after.