by skapacraft 1 (0 reviews)

LivQ AccessFix – EAA & A11y AutoFix

Name: LivQ AccessFix – EAA & A11y AutoFix
Author: skapacraft

Server-side WCAG 2.2 AA & EAA fixes for WordPress. Skip links, alt text, ARIA menus, heading checks, issues log, Accessibility Statement. Zero config.

LivQ AccessFix ranks #62,567 among WordPress.org plugins with 1+ active installations, is #329 of 765 in the Accessibility category, a 1/5 rating from 0 reviews, and was last updated Oct 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.1.1 Current Version v1.1.1

Updated 4 weeks ago Last Update on 03 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#329 of 765 in Accessibility Actively maintained

View on WordPress.org

Rank

#62,567

— No change

Active Installs

-75%

KW Avg Position

— No change

Downloads

481

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

49,630

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #62,567

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.1
Last Updated: Oct 03, 2026
Requires WP: 6.0+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: skapacraft

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

ARIA EAA a11y accessibility wcag

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades

100K+ installs

#360

Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)

100K+ installs

#428

404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring

100K+ installs

#429

Accessibility by UserWay

80K+ installs

#509

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness

20K+ installs

#1,116

View all Accessibility plugins

Frequently Asked Questions

Common questions about LivQ AccessFix – EAA & A11y AutoFix

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

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'; } );

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

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.

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.

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.

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.