| 开发者 | nareknovembit |
|---|---|
| 更新时间 | 2026年7月29日 23:57 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
a11yfleet folder to /wp-content/plugins/, or install the zip via Plugins → Add New → Upload.It helps you get there. The European Accessibility Act points to EN 301 549, which is based on WCAG 2.1 AA. A11yFleet checks your content against those WCAG criteria, reports what to fix, and generates a draft accessibility statement — the automatable groundwork for EAA compliance. Full compliance still requires manual review.
Yes. Every rule maps to a WCAG 2.1 success criterion at level A or AA, and the compliance report groups outstanding issues by criterion.
Yes. Web accessibility under both the ADA and Section 508 is assessed against WCAG, so the same checks apply. A11yFleet flags the machine-detectable WCAG issues those laws are concerned with.
No. No automated tool can. A11yFleet finds and helps you fix the machine-detectable issues and shows where manual review is still needed.
Published posts and pages by default. Choose post types in Settings, or use the a11yfleet_scannable_post_types filter.
No. Scanning runs on your own server, and the full-page scan requests only your own site's URLs. No data leaves your site.
It works on standard single-site installs and when activated on an individual site within a network (each site keeps its own data). Network-wide activation and a cross-site (network admin) dashboard are planned for a future release — for now, activate it per site rather than "Network Activate".