| 开发者 | nicodiangelo |
|---|---|
| 更新时间 | 2026年8月26日 00:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
stepless_accessibility_audit_recent_limit — how many recent posts/pages are scannedstepless_accessibility_audit_history_limit — how many past scans are keptstepless_accessibility_audit_findings_per_page — findings stored per pagestepless_accessibility_audit_nodes_per_finding — example elements per findingNo, and no plugin can. Automated testing catches roughly half of WCAG issues; the rest needs human judgement. This plugin finds and explains what a machine can detect, which is real, useful progress — but treating any scanner's clean result as legal compliance would be a mistake.
No. This plugin adds nothing to your front end. It reports issues in the WordPress admin so that you can correct them in your content, theme or templates.
No. The scan runs in your browser against your own pages, and the rule engine is served from your own site. The plugin makes no external HTTP requests of any kind.
No. Nothing is enqueued on your front end — no scripts, no styles, no extra queries. The plugin registers exactly one front-end filter, which hides the admin toolbar during a scan and returns immediately on every ordinary page view.
Your home page, your five most recently edited posts and pages, and — if WooCommerce is active — your shop, a product, the cart and the checkout.
Some pages send headers that stop them being loaded in a frame, which is how the scan reads them. When that happens the plugin says so plainly rather than reporting the page as clean, because a page that was not checked is not the same as a page with no problems.
WCAG 2.1 levels A and AA, which is the standard referenced by the European Accessibility Act, EN 301 549, and Section 508.
Yes. The scan reads your pages as a browser renders them, so it sees the final output regardless of how it was built.