A11yFleet
·
Scan content for accessibility issues, track them over time, and generate an EU Accessibility Act (WCAG 2.1 AA / EN 301 549) compliance report.
A11yFleet checks your posts and pages against WCAG 2.1 AA success criteria, scores each page, and shows exactly what to fix and why — with a compliance report and a draft accessibility statement aimed at the European Accessibility Act (EAA).
What it does
- Automated WCAG checks on content and on the full rendered page (theme header, nav and footer included): missing image alt text, non-descriptive link text, skipped heading levels, unlabelled form controls, buttons with no accessible name, duplicate IDs, empty headings, missing iframe titles, and missing document language.
- A dashboard listing pages that have issues, worst score first, with per-issue ignore / restore that persists across re-scans.
- An Accessibility panel in the block editor to scan the content you’re editing (before saving) or the full page, kept in sync with the dashboard.
- Background, batched scanning with an optional scheduled full-site scan (hourly, daily or weekly).
- A compliance report mapped to EN 301 549 with an auto-generated accessibility-statement draft, exportable to print/PDF or HTML.
Honesty note
Automated tools can only detect a portion of WCAG success criteria. A11yFleet does the automatable part well and clearly flags where human review is still required — it never claims a site is “100% compliant”.
Development
The admin JavaScript/CSS is built with @wordpress/scripts from the human-readable source in src/Admin/resources/. To build: npm install && npm run build. Composer, PHPCS/WPCS, PHPStan and PHPUnit are configured in the repository.
