BarrierForge — Accessibility Scanner
| 开发者 | dsweeneyjr |
|---|---|
| 更新时间 | 2026年10月15日 06:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Rendered-page scanning for up to 250 published public posts and pages.
- Checks for missing image alt attributes, empty links and buttons, generic link text, positive tabindex values, skipped heading levels, text contrast, and small touch targets.
- WCAG level and success-criterion references for each supported check.
- Administrator-only links that locate and highlight affected elements on the front end.
- Manual review and remediation tracking for small touch targets; unsafe automatic touch-target resizing is disabled.
- Opt-in sitewide enhancements for page language, a keyboard skip link, and visible keyboard focus.
- Remediation history and progress reporting that distinguishes open and resolved findings.
安装:
- Upload the BarrierForge ZIP from Plugins > Add New > Upload Plugin, or install it from the WordPress.org Plugin Directory.
- Activate BarrierForge.
- Open BarrierForge in the WordPress admin menu.
- Select Scan rendered pages to create the first Fix Queue.
- Review each finding before applying a fix or changing site content.
常见问题:
Does BarrierForge make my site legally compliant?
No. Automated tools cannot establish legal compliance or complete WCAG conformance. BarrierForge identifies a limited set of common barriers and helps administrators review them.
Does a scan change my content?
No. Scanning is read-only. The optional sitewide enhancements are opt-in and do not rewrite post content. Touch-target Auto Fix is disabled for safety; flagged elements require manual remediation.
Does BarrierForge send site data to an external service?
No. Scans run between the WordPress administration screen and pages on the same site. Scan results, remediation records, settings, and local usage counters are stored in the site's WordPress database and are not transmitted by BarrierForge to an external service.
What data is removed when I delete the plugin?
Deleting BarrierForge through the WordPress Plugins screen removes its scan results, settings, remediation records, and local usage counters.
Why can a page or element fail to scan or highlight?
Security headers, authentication rules, caching, or dynamically generated markup can prevent a rendered page from loading in the scanner or can change an element after a scan. BarrierForge preserves existing findings when a page cannot be loaded and reports when a saved element can no longer be found.
Are all WCAG success criteria tested?
No. WCAG levels and criterion numbers identify the standards related to checks that BarrierForge supports. Many WCAG requirements require human judgment and manual testing.
更新日志:
- Add Remediation History audit trail and import remaining saved remediation records.
- Preserve the 1.0.6 touch-target safety fix; previously deleted records require backup recovery.
- Safety: disable page-wide touch-target Auto Fix that could distort logos and navigation.
- Remove previously saved BarrierForge touch-target CSS while preserving unrelated theme CSS.
- Reopen touch-target findings previously marked auto-fixed for manual remediation.
- Improved plugin name and directory description for clearer accessibility-focused discoverability.
- Added rendered-page accessibility scanning and a filterable Fix Queue.
- Added affected-element evidence and administrator-only front-end highlighting.
- Added WCAG level, criterion, severity, and remediation progress reporting.
- Added reversible sitewide enhancements and supported automatic fixes.
- Added verified remediation history and safe handling for partial scan failures.
- Added complete data removal on uninstall and documented local data handling.