Web200 Accessibility Audit is a WordPress accessibility auditing and remediation toolkit focused on WCAG 2.2 workflows.
It helps teams detect, track, and remediate common accessibility issues directly in wp-admin, with practical tools for scanning, triage, reporting, and controlled remediation.
- Single URL scan and WooCommerce key-page scan
- Configurable scan engine: server HTML or rendered DOM with safe fallback
- Crawl mode for scanning multiple URLs
- WCAG issue list with severity, confidence, and remediation guidance
- Runtime remediation toggles with action history and rollback
- Source-fix workflows for post content with backup and rollback
- CI gate evaluation with release blockers summary and exportable evidence
- Pre-publish gate for editorial workflows
- Editor-side publish assistant with one-click gate check
- Compliance checklist workflow for WCAG 2.2 / EN 301 549
- Full WCAG 2.2 A/AA criteria matrix with status filters and evidence trace
- CSV, JSON, and HTML exports for reporting
- Admin diagnostics for environment, queue, scheduler, and integration status
This plugin is designed for real editorial and development teams that need:
- fast accessibility triage
- clear issue visibility
- deterministic remediation controls
- practical reporting workflows inside WordPress
- Upload the plugin files to the
/wp-content/plugins/web200-accessibility-auditdirectory, or install the plugin ZIP from the WordPress admin screen. - Activate the plugin through the Plugins screen in WordPress.
- Open Web200 Accessibility Audit in wp-admin to configure scanning and remediation.
No. The plugin provides deterministic runtime and source-level remediations for selected issue groups, plus guidance for manual fixes.
Compatibility depends on builder output and custom markup. The plugin includes builder context, scorecards, and targeted presets to improve coverage.
Yes. The plugin includes WooCommerce page targeting and accessibility checks for key store views.
- Web200 Accessibility Audit dashboard in wp-admin with scan summary, diagnostics, and recent issues
- Runtime accessibility toolbar and quick remediation controls on the frontend
- Security hardening: scan requests now explicitly enforce safe HTTP(S) scheme checks and reject credentialed URLs.
- Security hardening: server-side HTML fetch now uses unsafe-URL rejection, explicit SSL verification, and response size limits.
- Security hardening: scanner now rejects non-2xx HTTP responses and non-HTML content types before parsing.
- Reworked runtime/frontend CSS output to use WordPress enqueue hooks and inline style APIs instead of direct style tag output
- Reworked source-fix focus remediation to inject CSS classes and use enqueued stylesheet assets
- Added missing translators comments for placeholder-based i18n strings in pre-publish gate notices
- Hardened list-table helper output paths and documented safe escaped HTML output for PHPCS/WPCS
- Improved option lock-key prefix usage in action processing lock writes
- Reworked CSV export writer to avoid direct file-stream operations
- Improved CI gate triage in post/page lists with clickable counters and clickable legend badges
- Added one-click All filter reset in CI gate counters
- Added per-user, per-post-type memory of the last selected CI gate filter
- Extended smoke tests for CI gate filters, links, legend actions, and user preference persistence
- Initial stable release with scan, remediation, exports, diagnostics, and compliance workflow
Review hardening release for WordPress.org checks, including enqueue handling, i18n comments, escaping, option-prefix consistency, and export internals.
- WordPress 6.4 or higher
- Tested up to WordPress 6.9
- PHP 8.1 or higher
WEB 200 Tomasz Latusek
Website: https://web200.pl/
For product information and support, visit:
https://web200.pl/
GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html