Dutch regulator ACM found 61% of major webshops still fail basic screen-reader checkout (24 Mar 2026). See What Gets Checked

Docs & FAQ

What True Access Now actually checks and fixes, what each plan includes, and honest answers to the questions we get most.

What gets checked, tier by tier

Free — static scan, runs entirely inside WordPress

Missing or low-quality image alt text, heading structure (skipped levels, multiple H1s), generic link text ("click here", "read more"), the site's lang attribute, table header scope, and aria-label on evident icon-only links/buttons. Runs in phased batches via WP-Cron so large sites don't hit PHP time limits. Every finding is kept in a permanent audit log, including resolved issues with their resolution date.

Pro / Agency — adds a real-browser scan

A hosted service (Playwright + axe-core) opens your live pages in an actual browser to check color contrast and keyboard-navigation focus order — things that only exist after CSS and JavaScript run, which a static PHP scan structurally cannot see. This is also what catches issues inside JS-rendered page-builder markup (Elementor, Divi, and similar). Plus: unlimited PDF audit-log export (the free dashboard view caps at 20 rows for readability; the export never does), and WHMCS-backed licensing — 1 domain on Pro, up to 10 on Agency.

What gets fixed automatically — and what doesn't

Safe to auto-fix (opt-in, off by default)

Three narrow, deterministic fixes: a missing lang attribute, a missing scope on a table header, and a missing aria-label on an icon-only link/button that's clearly recognizable (social icons, a mailto: or tel: link). Each one only acts when nothing is already set — it never overwrites an existing value, and it never guesses.

Signalled only, on purpose

Color contrast and keyboard-navigation issues are never auto-fixed. Fixing those usually means a real design or code change, and an automated tool guessing wrong could break your layout or your theme. These stay as flagged, actionable issues in your audit log for a developer to review — which is also why an agency plan exists.

Frequently asked questions

Is this an overlay/accessibility widget?

No. Overlay widgets add a floating button that lets a visitor tweak font size or contrast in their own browser — they don't change your site's actual HTML, and they don't produce demonstrable compliance (some overlay vendors have even been sued for claiming otherwise). True Access Now scans and, for a narrow set of safe cases, fixes your site's real markup, and keeps a permanent record of what was found and fixed.

Does this guarantee EAA/WCAG compliance?

No, and treat any tool that claims it does with real skepticism. True Access Now finds concrete, fixable issues and documents your remediation history as evidence of ongoing effort. Full compliance also depends on things outside any scanner's reach — content decisions, PDFs, video captions, and more. See the full disclaimer in our Terms of Service.

Will an automatic fix ever change something that already works?

No. Every auto-fix is opt-in and only acts when nothing is already set for that element — see "What gets fixed automatically" above.

What happens to my data if I remove the plugin?

Your audit log is kept, the same as during a normal update — only the plugin files are removed. There's a separate, explicit "Delete all my accessibility data permanently" action (with a typed domain confirmation) in the plugin's settings if you want to erase it for good.

Which languages are supported?

The plugin interface is available in Dutch, English, and German.

I have a question this page doesn't answer.

Reach us at support@trueaccessnow.com.