WordPress plugin · free

Find the accessibility problems in your WordPress site — and see the exact markup that causes each one.

AccessAudit scans your own pages and reports what a machine can actually see in your HTML: images with no alt text, icon links and empty buttons with no accessible name, form fields with no label, heading levels that skip, tables with no header cells, frames with no title, positive tabindex values, `aria-hidden` elements that still take focus, duplicate ids and zoom-blocking viewport settings.

Install it free from WordPress.org What no plugin can check Fix the ten most common problems See a sample client report Help and answers Pricing for agencies Try the live demonstration See how it works Instead of an overlay widget Checking contrast by hand Write an accessibility statement Check a page free

What you get

What it refuses to do

What the paid version adds

For agencies and anyone who looks after several sites: scheduled rescans with email alerts that fire only when something new appears, a list of what got fixed since last time, unlimited pages, and a print-ready report you can put your own name on.

Who it is for

Site owners who want to know what is actually broken before hiring anyone, and agencies who need a concrete, checkable list to work from. It is a finding tool, not a magic fix.

Install

  1. In WordPress, go to Plugins → Add New and search for AccessAudit, or download the zip from the plugin page and upload it.
  2. Activate it, then open AccessAudit in the admin menu.
  3. Press Run a scan now. Fix the mark-up. Run it again.

Free version: up to 50 pages per scan, CSV export included. A paid version is planned for people who do this for clients: scheduled rescans with email alerts, unlimited pages, history, and multi-site reporting. Tell us which one you need and it gets built first.

Why you can trust the findings

Every finding quotes the exact piece of markup it is complaining about, so you can verify it yourself in ten seconds. If a finding is wrong, it is obvious — and we want to hear about it. The plugin ships with a regression test: a page full of known problems must produce exactly the expected findings, and a clean page must produce none.