AuditWand Accessibility

No, and be wary of any tool that says yes. No automated tool can. AuditWand finds a substantial subset of accessibility issues automatically, explains how to fix them, fixes the mechanical ones, and documents your ongoing effort. Fixing what it finds improves accessibility. Full conformance also requires human review: judging whether alt text describes an image, whether captions are accurate, whether content is understandable. Those are the parts no engine can test, and AuditWand says so on every clean result.

No account is needed for the local layer: unlimited page checks (they run locally in the editor), all 16 one-click fixes, auto-check on save, the Media Library Audit, and dismiss-with-reason with the complete Ignore Log all work on a fresh install with no connection. A free account connects your site for the cloud service and adds the badge and public status page; paid plans add site scans of every page, scheduled scans, history and trends, regression alerts, hosted statements, and PDF reports.

Before you connect: nothing. The plugin makes no outbound request of any kind, and an automated test suite proves it on every release. After you connect: your server sends your site address and page URLs to the AuditWand API, authenticated with your connect key, and site scans store findings with short HTML snippets from your public pages. Editor page checks run in your browser; the content you are editing is never sent. After a check completes, the plugin reports a bare counter (a check happened, and when) so your public status page can show activity. Everything is stored in the EU (Frankfurt). Deleting a site or your account removes it.

Small, safe corrections to the HTML your site sends to visitors: a skip link, visible keyboard focus, underlined content links, labels on the search box, comment fields, and placeholder-only form fields, the page language attribute, zoom allowed on phones, forced tab order removed, redundant tooltips removed, a note on links that open new tabs (or those links kept in the same tab), a fallback page title, file type and size on document links, PDF uploads blocked, and a footer link to your accessibility statement. Nothing changes in your database or your content. Each fix shows a before-and-after preview, can be turned off with one click, and is logged with a timestamp. With every fix off, your site's output is byte-for-byte what it was without the plugin.

No. Overlays inject a script into the visitor's browser that tries to patch the page after it loads. They are widely criticized by the accessibility community, regulators have acted against vendors who claimed such tools deliver compliance, and sites using them continue to receive complaints and claims. AuditWand ships zero visitor-side JavaScript. Its fixes are real server-side corrections to your site's HTML, and everything else it does is detection, guidance, and record-keeping.

No. With every fix off, the plugin adds nothing to your site's front end: no scripts, no styles, no requests. Each fix you enable adds only its own HTML change and, for a few fixes, a few hundred bytes of inline CSS. Site scans run on AuditWand's servers, which visit your public pages the way an ordinary visitor does, with a small number of parallel page workers and a polite pace. The whole plugin is 283 KB.

Every feature works from the AuditWand admin menu regardless of editor. The in-editor "Accessibility" box with the instant "Check this page" button appears in the block editor and the Classic Editor. Page-builder edit screens (Elementor, Divi, Beaver Builder, and others) cannot host the box; use the Pages tab in the AuditWand menu to see per-page findings, then open the page in your builder to fix them. Site scans and issue tracking behave identically for every editor.

Every combination of WordPress 6.5, 6.8, 7.0, and 7.1 with PHP 7.4, 8.1, 8.3, and 8.4: sixteen combinations, each booted with debugging on, every admin screen and the editor walked, and zero PHP notices. Also a classic-widgets theme (Twenty Twenty-One), a block theme (Twenty Twenty-Five), Astra, and multisite with network-wide activation. Builders: pages built in Elementor and Beaver Builder Lite, scanned, fixed, and marked by View on page. AuditWand works with any theme or builder that outputs standard HTML, because scans and fixes operate on the final rendered output. Issue tracking survives builder re-saves because issue fingerprints ignore builder-generated markup noise, and themes that declare the accessibility-ready tag never get the skip-link and focus fixes applied twice.

Email support@auditwand.com or post in the plugin forum at https://wordpress.org/support/plugin/auditwand-accessibility. Replies typically arrive within 1 to 2 business days. There is no phone line and no 24/7 desk; AuditWand is a one-person company with automated systems as the team, and we say so wherever support is mentioned. If you are facing litigation or need a formal audit, engage an accessibility professional: AuditWand is automated tooling for finding, fixing, monitoring, and documenting accessibility work, not an audit service and not legal advice.

EU accessibility rules generally expect an accessibility statement, a way for visitors to report problems, and evidence of ongoing effort. On the free plan, AuditWand generates an accessibility statement template pre-filled with your site's known limitations, and the public status page carries a visitor feedback form. The fix log and the Ignore Log with reasons are your dated evidence trail. Pro adds a hosted statement that updates itself from scan data and dated PDF reports mapped to EN 301 549 clauses. None of these documents claims compliance on your behalf; they describe what was checked, what was found, and what was done.

The plugin works anywhere. Its interface is in English today and is translation-ready; German and French listing text is published, and translations are welcome through translate.wordpress.org. The Business plan delivers reports in French and German. Consumer purchases from Quebec are not accepted until French-language terms of service exist, in keeping with the Charter of the French Language; business customers in Quebec can subscribe.

Every paid plan carries a 30-day money-back guarantee: email support within 30 days of your first payment and the payment is refunded in full. Statutory rights, including the EU 14-day right of withdrawal, are unaffected. Renewals are disclosed before purchase with the price and term, and cancellation is self-serve with no barriers. Details: https://auditwand.com/legal/refunds

In your dashboard, open Settings › Account and choose Delete account. Deletion is immediate and cascades through every site, scan, issue, and record on the account. You can also email privacy@auditwand.com from your account address and we complete it within 30 days. Uninstalling the plugin removes every option it created on your site.

The Business plan covers 5 sites with 3 team seats in one dashboard, so an agency can run several client sites from one account. Team members act inside the owner's account with their own sign-in. The locked disclaimer on every report stays in place, because it protects your clients as much as it protects us.

The score starts at 100 and subtracts points for each open issue found by automated checks: 10 for critical, 5 for serious, 2 for moderate, 0.5 for minor. It never goes below zero. Items under "Worth reviewing" do not affect it, because they need human judgment. It is a progress meter, not a certificate. A rising score means fewer and less severe problems. It is not a compliance percentage, because automated checks test only part of the rules.

Email security@auditwand.com. Report privately rather than opening a public thread. We aim to acknowledge reports within 48 hours. Details: https://auditwand.com/.well-known/security.txt

Nothing breaks. Fixes you applied keep running, because they run on your own site. You keep the free layer in full. Paid surfaces lock again until you return, and your history is kept for the retention period stated in the Privacy Policy.

The plugin is translation-ready with a complete language template, and the listing is published in English, German, and French. Interface translations arrive through translate.wordpress.org as contributors complete them; if you would like to help with a language, the project is open there.