Connect your WordPress site to Garsen Accessibility Guard for automated WCAG accessibility scanning and reporting.
Garsen Accessibility Guard is a WordPress plugin that connects your site to the Garsen Accessibility Guard platform for automated WCAG accessibility scanning and compliance reporting.
External Service Disclosure
This plugin connects to the Garsen Accessibility Guard platform (https://wcag-guard.com) to perform accessibility scans. The plugin requires an active connection to this external service to function.
Data transmitted:
- Your site URL (for scanning purposes)
- API key (for authentication)
When data is sent:
- When you run an accessibility scan (on-demand or scheduled)
- When verifying API connection status
- When retrieving scan results
Service links:
Features:
- Connect your WordPress site to Garsen Accessibility Guard
- Run on-demand accessibility scans
- Schedule automatic daily or weekly scans
- View scan status and issue summaries directly in WordPress
- Access detailed reports in the Garsen Accessibility Guard dashboard
Note: This plugin requires an active Garsen Accessibility Guard account and API key. Visit wcag-guard.com to create an account.
Screenshots
Dashboard showing connection status and scan results
Do I need a Garsen Accessibility Guard account?
Yes, this plugin connects to the Garsen Accessibility Guard platform. You need an active account and API key to use this plugin.
Where do I get my API key?
Log in to your Garsen Accessibility Guard account at wcag-guard.com and navigate to Settings > API Keys to generate a new API key.
Does this plugin run accessibility audits locally?
No, this plugin connects to the Garsen Accessibility Guard platform which performs the actual accessibility analysis. The plugin handles communication with the API, triggering scans, and displaying results.
How often can I run scans?
You can run scans on-demand at any time, or schedule automatic scans daily or weekly.
What accessibility standards are checked?
Garsen Accessibility Guard checks against WCAG 2.1 Level A and AA guidelines. See the documentation for a complete list of rules.
ChangeLog
1.2.8
- Fixed: Maintenance release with recent fixes and stability improvements.
1.2.7
- Fixed: WordPress.org deployment packaging now excludes hidden development directories from trunk and tags.
- Fixed: Release metadata aligned for 1.2.7 publication.
1.2.6
- Fixed: Issues page now reads issues from API response data field and loads with limit=200.
- Added: Report Language selector in Settings (manual override + auto-detect option).
- Fixed: Report language persistence (defaults, sanitization, and save flow).
- Fixed: Accessibility Statement language dropdown now honors saved report language.
- Fixed: Removed discouraged manual load_plugin_textdomain() call (WordPress.org compliance).
1.2.5
- Fixed: Plugin header Author field now uses plain text (WordPress.org compliance)
- Fixed: Removed directory asset files from plugin distribution zip
- Fixed: Replaced deprecated current_time(‘timestamp’) calls
- Fixed: Improved output escaping on dashboard severity bars
- Fixed: Excluded unused vendor files from distribution
1.2.4
- Fixed: Text domain mismatch errors – all i18n strings now use correct text domain
- Fixed: Plugin folder name reference in installation instructions
- Fixed: Consistent branding throughout UI
1.2.3
- Security: Improved API key encryption with AES-256-GCM and AAD
- Added: PDF and CSV report export support (PRO feature)
- Added: Scan history page with detailed issue breakdown
- Added: Scan detail page with issue diagnostics
- Added: Alert preferences and webhook configuration
- Added: Account tier and quota display
- Improved: Connect Flow with direct email registration
- Improved: Better error handling and user feedback
- Fixed: Various bug fixes and performance improvements
1.0.0
- Initial release
- Connect to Garsen Accessibility Guard
- Run on-demand scans
- Schedule automatic scans (daily/weekly)
- View scan status and issue summaries
- Link to detailed reports
