Accessibility Guard
Accessibility Guard
Description
Accessibility Guard scans your WordPress pages for WCAG 2.2 accessibility issues and helps you fix them. Unlike overlay widgets that mask problems without fixing them, this plugin identifies issues at the source code level.
20+ WCAG 2.2 Checks Including:
- Missing image alt text (WCAG 1.1.1)
- Empty links and buttons (WCAG 2.4.4)
- Color contrast ratio (WCAG 1.4.3)
- Heading hierarchy (WCAG 1.3.1)
- Missing form labels (WCAG 1.3.1)
- Missing document language (WCAG 3.1.1)
- Removed focus indicators (WCAG 2.4.7)
- Missing ARIA landmarks (WCAG 1.3.1)
- Empty table headers (WCAG 1.3.1)
- Missing skip navigation (WCAG 2.4.1)
- Duplicate element IDs (WCAG 4.1.1)
- Auto-playing media (WCAG 1.4.2)
- Restrictive viewport meta (WCAG 1.4.4)
- And more…
Auto-Fix Features:
- Inject skip navigation link
- Ensure HTML lang attribute
- Remove empty headings
- Add missing form labels (screen-reader friendly)
Accessibility Statement Generator:
Generate a complete accessibility statement page with your organization details, conformance target, and known limitations.
Dashboard:
- Summary cards showing total issues, pages scanned, and compliance percentage
- Per-page issue details with severity, WCAG reference, and element snippets
- A11y status column in Posts/Pages list tables
- Bulk scan all pages with progress indicator
Installation
- Upload the
accessibility-guardfolder to/wp-content/plugins/ - Activate the plugin through the ‘Plugins’ menu in WordPress
- Go to A11y Guard in the admin sidebar
- Click Scan All Pages to run your first scan
- Configure auto-fixes in A11y Guard > Settings
Faq
No. Accessibility Guard is a scanner that identifies issues in your actual page HTML. It does not inject a toolbar or overlay widget. Auto-fixes modify the source output, not a JavaScript layer.
No automated tool can guarantee full WCAG compliance. Approximately 40% of WCAG criteria can be tested automatically. Accessibility Guard helps you identify and fix the issues that can be detected programmatically.
Yes. The scanner works with any page builder (Elementor, Divi, etc.) because it scans the rendered HTML output, not the builder’s internal data.
No. Scanning happens only in the WordPress admin via AJAX. The only front-end impact is from auto-fixes (skip link, lang attribute), which are minimal.
Reviews
Changelog
1.0.0
- Initial release
- 20+ WCAG 2.2 accessibility checks
- AJAX-based per-page and bulk scanning
- Auto-fix: skip links, lang attribute, empty headings, form labels
- Accessibility statement page generator
- Admin dashboard with summary cards and issues table
- A11y status column in post/page list tables
- Scan results caching via transients