LivQ AccessFix – EAA & A11y AutoFix

开发者	livqtech danielegagliardi
更新时间	2026年7月18日 18:52
PHP版本:	7.4 及以上
WordPress版本:	7.0
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

LivQ AccessFix – EAA & A11y AutoFix applies WCAG 2.2 AA and European Accessibility Act (EAA) remediations automatically, intercepting the full rendered HTML via PHP output buffering before it reaches the browser - not after, not via JavaScript overlay. Every module can be independently enabled or disabled from Settings → LivQ AccessFix.

安装:

Upload the livq-accessfix folder to /wp-content/plugins/.
Activate the plugin through the Plugins screen.
Navigate to Settings → LivQ AccessFix - all modules are enabled by default.

No configuration is required for immediate effect.

屏幕截图:

常见问题:

Will this plugin break my theme?

No. All frontend changes are applied as output filters - database content is never modified. Deactivating the plugin instantly removes all effects.

Does it work with Elementor, Divi, or other page builders?

Yes. The PHP output buffer is automatically skipped when a visual editor is detected, preventing any interference with the builder's own rendering pipeline.

The skip link targets #primary. My theme uses a different ID.

Use the Auto-detect button in Settings → LivQ AccessFix → Configuration, or override via filter: add_filter( 'livqacea_skip_link_target', function() { return '#main-content'; } );

Does the focus CSS override my theme's existing focus styles?

Yes, intentionally. The focus-visible rule uses !important to override outline: none resets. To customise colours, disable this module and add your own CSS.

Are JS-based accessibility overlays legally compliant under EAA?

Multiple accessibility organisations (NFB, ACB) and legal precedents have held that JS overlays do not constitute genuine WCAG compliance because the underlying HTML remains inaccessible. LivQ AccessFix fixes the source HTML server-side, which is what automated auditors (axe, WAVE, Lighthouse) and legal evaluators assess.

Where is the Accessibility Statement shortcode?

Go to Settings → A11y Statement, configure your organisation details, then embed [livqacea_accessibility_statement] on any page. Use the one-click helper to create a pre-configured draft page automatically.

What does the confirmation checkbox on the Statement page do?

It records a timestamped declaration (user name, email, date, plugin version, site URL) in the database. This provides legal evidence that an authorised operator reviewed and accepted responsibility for the statement content, as required by EAA 2025.

Does the Accessibility Scanner modify my site?

No. The scanner fetches each page as an anonymous visitor would and analyses the received HTML. Nothing is written to the database during a scan - only the results are cached.

更新日志: