Automated web accessibility testing against WCAG 2.2, on every merge.
Automated accessibility testing in ZeuZ runs a WCAG 2.2 scan on the page your functional test just reached, after login and after the interaction, so Section 508 and European Accessibility Act failures surface on the merge that caused them. Three reports per run, kept as evidence.
Automated accessibility testing checks a rendered web page against the Web Content Accessibility Guidelines, WCAG 2.2, for failures a program can detect, missing alternative text, contrast, labels, roles and keyboard traps, so Section 508 and European Accessibility Act obligations are checked continuously rather than before an audit. ZeuZ runs the scan as a step inside a functional test, on the page as the user reaches it, and keeps the report with the run.
Where web accessibility testing breaks today.
The scan runs on the public homepage, and the failures live behind login, on the third screen of the flow the scanner never reaches.
Accessibility is audited once a year by a vendor, so twelve months of merges ship before anyone looks.
The report is a PDF nobody can trace to a commit, so the developer fixes it by guessing which release introduced it.
How ZeuZ automates accessibility testing.
- 01Test designProposes which screens need a WCAG check from the changed templates and components, so the scan follows the change.
- 02Test case creationAdd the check in plain English, "then run an accessibility test on this page"; it becomes a step in the existing case.
- 03Test automationThe step runs an axe-based scan on the rendered page in the browser session, after login and after the interaction.
- 04Test executionRuns with the functional suite on every merge or on a schedule, on your own nodes.
- 05Reporting and analysisThree reports per run, an HTML summary, a JSON summary and the raw results, each violation with its element and WCAG criterion.
- 06Test maintenanceThe check lives in the case, so when the flow changes the scan moves with it and a locator break comes back as a proposed repair.
Your team reviews what ZeuZ produced. Nothing joins the suite or runs without a person accepting it.
See it run on your application.
Watch a WCAG 2.2 check run inside your own functional suite, live.
Accessibility testing tools inside the functional suite.
The ZeuZ accessibility test action evaluates the page currently rendered in the Selenium WebDriver session against WCAG guidelines using the axe engine, through axe-selenium-python. That means the scan runs after any login, navigation or interaction the test has already performed, rather than on a cold public URL, and it needs no parameters beyond an optional wait. This is where automated accessibility testing stops being a separate crawler and becomes a step in the case.
Every run produces three files, an HTML report for people, a JSON summary for dashboards and the raw results for auditors, stored with the run. Findings name the element, the rule and the criterion, which is what a WCAG 2.2 A or AA conformance record needs. Automated checks cover the portion of WCAG a program can decide; the rest, screen-reader flow, focus order judgement and meaning, is manual work ZeuZ's managed QA team performs against the same suite.
- Engine
- axe, via axe-selenium-python
- Standard
- WCAG 2.2 A and AA automated rules
- Runs on
- The rendered page in the test's browser session, after login
- Reports
- HTML summary, JSON summary, raw JSON, per run
- Evidence
- Element, rule and criterion per finding, pinned to the run
- Manual coverage
- Screen reader and focus review through managed QA services
Runs where your code is allowed to be.
Hosted by ZeuZ, execution on your own machines.
Point the client at your own server.
Disconnected environments, scoped per engagement.
Runs inside Jenkins, GitHub Actions, Azure DevOps, CircleCI and Bitbucket; results into Jira, Slack and Teams.
Works in the same suite as.
The functional checks the accessibility step rides inside, on the same pages.
GUI testing →The same pages checked across the browsers your users run.
Cross-browser testing →The other compliance scan that belongs on every merge, in the same suite.
Security testing →Read next: QA automation services →Related: Manual accessibility review →
What is web accessibility testing?
+
Web accessibility testing checks that a site works for people with disabilities, screen reader users, keyboard-only users, people with low vision, against the Web Content Accessibility Guidelines, which Section 508 and the European Accessibility Act reference. Part of WCAG is programmatically checkable, alt text, contrast, labels, roles; the rest needs human judgement. ZeuZ runs the automated portion as a step inside a functional test and keeps the report with the run.
Try ZeuZ Free →How do you automate accessibility testing?
+
Put the scan where the page state is real: after login, after navigation, after the interaction that renders the content. In ZeuZ you add one plain-English step, "then run an accessibility test on this page", and the axe engine evaluates the page rendered in the same browser session against WCAG 2.2 automated rules, on every merge or on a schedule, producing an HTML report, a JSON summary and the raw results per run.
Try ZeuZ Free →How do you test screen reader accessibility?
+
Screen reader testing is manual: a person navigates the flow with NVDA, JAWS or VoiceOver and judges reading order, announcements and focus behaviour, which no automated rule can decide. Automated checks catch the failures that break screen readers before the session starts, missing alt text, labels and roles. ZeuZ runs those checks in the suite, and its managed QA team performs the screen reader and focus review against the same suite.
Try ZeuZ Free →Can automated tools catch every WCAG issue?
+
No. Automated checks decide the portion of WCAG a program can evaluate, alt text, contrast, labels, roles, keyboard traps, and cannot judge reading order, focus logic or whether an alt text is meaningful. Treat the scan as the continuous layer and the human review as the conformance layer. ZeuZ runs the automated layer on every merge, and the manual review is available through its managed QA services.
QA automation services →How do you evidence WCAG 2.2 conformance for an audit?
+
Keep dated, per-run records that name the page state, the rule set and each finding with its element and criterion, so an auditor can trace a result to a build. ZeuZ stores three reports with every run, an HTML summary, a JSON summary and the raw results, each finding carrying the element, the rule and the WCAG criterion, pinned to the run that produced it.
Try ZeuZ Free →Ready to automate QA testing today?
See ZeuZ Test Studio write, run and repair tests against your own application code.
or explore our services →