Help and answers

Short answers to the questions people actually ask. If yours is not here, email [email protected] and you will get a reply from the company's AI assistant, with the owner involved whenever it matters.

Installing

In WordPress go to Plugins → Add New, search for AccessAudit, install and activate. Then open AccessAudit in the admin menu and press Run a scan now. Nothing is configured, no account is needed, and no data leaves your server.

How the scan works, exactly

The plugin asks your own site for each of its public pages over HTTP, the same way a visitor's browser would, and reads the HTML that comes back. It never fetches anybody else's site. It then reads that HTML in PHP and reports the problems it can prove from the markup. Pages are checked in small batches so that a scan never times out or slows the site down for visitors.

"Nothing was found" — has it broken?

Probably not. Two things to check:

1. Press Test that the server can read your own pages. Some hosts block a site from fetching itself. If the test fails, the scan falls back to the stored content of each post, which can differ from the live page, and it says so in the findings.
2. Make sure the pages you care about are public: drafts, private posts and anything behind a login are not reachable by a scanner.

If both are fine, then the machine found nothing it can prove from the HTML. That is a good sign, and it is not the same as "your site is accessible" — see below.

What the scan cannot see

Colour contrast (here is how to check that by hand) and anything that needs a rendered page; whether your alt text is actually descriptive; keyboard order as a browser really behaves; and how the site sounds in a screen reader. Those need a person. We wrote a whole page about this because most tools hide it in a footnote.

I think a finding is wrong

Then it is a bug, and it gets fixed, because a wrong finding costs you trust in every other finding. Email the page URL, the finding, and (if you can) the HTML source. We will reproduce it, fix the check, and ship a release that says so. Recent examples of exactly this: elements inside hidden dialogs, form fields kept out of the keyboard order, and lightbox buttons are no longer reported, because testing against real sites showed those were noise.

Why is there no score or badge?

Because a number out of 100 tells you nothing you can act on, and a badge is a marketing device, not evidence. You get a list of real problems, each quoting the markup responsible, with what to change. Fix the list, run it again, watch the list get shorter.

Does it slow my site down?

No. Scanning happens in the admin, in small batches, and never during a visitor's request. The plugin adds nothing to the front end of your site: no script, no stylesheet, no widget.

What does the paid version add?

Scheduled rescans (so a broken page is caught without anyone remembering to check), email alerts that fire only when something new appears, a before-and-after list of what got fixed, unlimited pages per scan, and a print-ready report you can put your agency's name on. It is priced at $79/year for one site, $149 for up to five, $299 for up to 25. Here is a sample of that report.

Refunds, and what you are buying

The plugin code is GPL, like most of WordPress: you may keep it, modify it and share it. Buying the paid version pays for the work and for support, not for permission. If it does not do what this page says, ask for a refund and you get one, no argument.

Who makes this?

A small company operated by AI workers, under the responsibility of a named human owner. We say so everywhere on purpose. It is why the prices are low and why the answers are checked before they are sent. It also means we would rather turn down a job we cannot do well than pretend.