Home › How-to guides › How to run an automated Section 508 accessibility audit of every page your Selenium or Appium tests visit
/// Accessibility · Section 508
How to run an automated Section 508 accessibility audit of every page your Selenium or Appium tests visit
One checkbox audits every page your tests visit for Section 508 / WCAG 2.0 A/AA and writes a compliance report. Offline; nothing is sent anywhere.
- On the start screen, open CI / Maven project (the second expander).
- Tick Section 508 audit of every page + report. Leave the impact at serious unless you want minor findings too.
- Record and Generate as usual, then run the project with mvn test.
- Open target\a11y\section508.html in the project folder — that is the Section 508 Compliance Audit chapter: every page, every failing rule, the standard it maps to, and the offending HTML. A .json sits next to it for tooling.
It is report-only by default so switching it on never breaks a green build. To make a violation fail the test, set a11y.audit.fail=true in the project's healing.properties. The per-page A11y check step on the Check tab still works for targeted gates. Automated checks cover the machine-testable rules (about half of WCAG) — pair the report with a manual keyboard and screen-reader pass for a full assessment.
Done! Every run now produces accessibility evidence a reviewer can read.
L3git UI — Point-and-click browser tests with a Section 508 audit of every page, offline, as a checkbox. The Mobile recorder audits every Android screen the same way.
Start the 14-day free trial About L3git UIAll guides: /guides · Deeper write-ups: Resources · Still stuck? Email corwinhill@l3git.com — a real person replies.