| 开发者 | securepilot |
|---|---|
| 更新时间 | 2026年8月1日 22:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
composer install inside the plugin directory (without it, PDF export falls back to a printable HTML report)./wp-content/plugins/securepilot-accessibility-scanner.composer install to install Dompdf (optional, enables PDF export).npm install && npm run build to build the React dashboard assets.No. It automatically catches a useful set of common, machine-detectable issues, but a handful of checks (focus indicators, third-party embedded video captions) are heuristics flagged for manual review, and many WCAG success criteria (e.g. meaningful reading order, keyboard traps, correct ARIA usage) require human judgment or a full browser to evaluate. Treat this as a first pass, not a substitute for a manual audit.
Contrast checking only evaluates colors declared directly in an element's style attribute. Colors set via an external stylesheet or theme CSS require a real browser to compute, which is out of scope for a server-side scan.
By default, nothing is deleted — your scan history and settings remain in the database if you reactivate later. If you want a full cleanup on uninstall, enable "Delete data on uninstall" in Settings before removing the plugin.
In a dedicated wp_accessibility_issues table, one row per detected issue, with its status (open, resolved, or ignored), severity, and the specific standards clause it violates.