Accessibility Checker – WCAG 2.1 AA, EAA & Section 508 Site Audit – QAProof
Free WCAG 2.1 AA accessibility checker. Scan one page or your whole site, and see what changed since last time. No account for the first check.
Solid choice
Accessibility Checker is a solid plugin choice in 2026, with a few things worth checking first. Is rated 5/5 and was last updated 3 days ago, and scores 71/100 on our health check.
- Actively developed — last update 3 days ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Accessibility Checker stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| a11y | #48 |
| accessibility | >100 |
| accessibility checker | #29 |
| EAA | #24 |
| wcag | >100 |
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Accessibility Checker
From the official readme · v1.0.45Description
Find out where your site fails WCAG — before anyone else does.
Install the plugin, click one button, and QAProof loads your home page in a real
browser and checks it against WCAG 2.1 Level AA. You get a score and the
issues it found straight away. No account, no API key, nothing to configure
for that first check.
It is an accessibility scanner, not an overlay or a toolbar: it changes nothing
on your site and shows nothing to your visitors. It finds a11y defects and tells
you where they are, so you or your developer can fix them properly — the
approach the accessibility community asks for, and the one that stands up when
someone checks your work against WCAG, EN 301 549, the European Accessibility
Act (EAA) or Section 508.
What it checks
QAProof runs the checks that can be made automatically, and tells you exactly
where each one failed:
- Colour contrast (color contrast) — text and UI borders measured against the 4.5:1 and 3:1 thresholds, with the computed colours it used.
- Images without alt text — and alt text that is a file name, a placeholder word, or far too long.
- Form fields without labels — including fields whose only label is a placeholder, which disappears as soon as someone types.
- Keyboard focus — controls with
outline: noneand no visible focus style, which strand keyboard users. - Heading structure — skipped levels, empty headings, more than one H1.
- ARIA — invalid roles and roles missing the attributes they cannot work without.
- Landmarks — content sitting outside any navigable region.
- Touch targets — controls below the 24×24px minimum.
- Page language — a missing or malformed
langattribute, which decides how a screen reader pronounces your page.
Every finding names the WCAG success criterion it relates to, the exact
element (CSS selector and a snippet of the source) and what was measured —
the actual contrast ratio, the actual size — so you can check it yourself
rather than take our word for it.
An honest word about “compliance”
Automated checks find a meaningful share of accessibility problems, and they
find them in minutes. They cannot tell you that a site is compliant.
No automated tool can judge whether your alt text is meaningful, whether your
tab order makes sense, or whether a screen reader user can actually complete
your checkout. Standards like EN 301 549, the European Accessibility
Act, Section 508 and Italy’s AgID guidelines all expect manual
testing with a keyboard and a screen reader.
Use this to find what can be found quickly, to measure whether you are getting
better, and to hand a developer a precise list. Do not use it as a compliance
certificate — and be sceptical of any tool that offers you one.
Check the whole site, not one page
Site Audit finds your pages from your sitemap and checks every one of them,
then does the thing a page-by-page list cannot: it groups the findings.
On a WordPress site most defects live in a template, so the same problem
appears on every page that uses it. Instead of reporting it forty times, Site
Audit says “this one fix covers 38 pages” — and sorts the list so the
fix with the widest reach is at the top.
Run it again after the work is done and you get the other half: what changed
since last time. How many issues were resolved, which ones, on which pages,
and anything new that appeared. That is the part you can show a client.
Coverage is always stated plainly — how many pages were checked out of how many
were found, and which ones could not be loaded. A page behind a bot wall or one
that times out is reported as exactly that, and never counted as passing.
How many pages one run checks depends on your plan: 5 on the free plan, 50
on Pro, 150 on Business. The report always says how many it found so you can
see what was left out. When a run finishes, a copy of the report is emailed to
the address on your account.
Beyond accessibility
The same plugin also covers the visual side of QA, if you need it:
Design Fidelity
Does the live site actually match the design?
The situation: “I sent the mockup to the developer and the result looks nothing like it. I spend hours comparing elements by eye — and still miss things.”
What you get: Connect your Figma account and pick a design — QAProof compares it against your live page. Every layout shift, color mismatch, typography difference, and spacing issue is flagged with its exact location and a copy-paste CSS fix.
Responsive Testing
Does your site hold together on every screen size?
The situation: “Everything looks fine on my phone. Then a client calls from their iPad and says half the page is broken.”
What you get: Your page is tested at five viewports — desktop, tablet (portrait and landscape) and mobile (portrait and landscape). The AI identifies overflow, broken stacks, illegible text, and layout failures across all five viewports — not just the device you happened to check.
Visual Regression Monitoring
Did the last update break something you haven’t noticed yet?
The situation: “After a plugin update, the header shifted and a button disappeared. We only found out a week later — when a client complained.”
What you get: Set a baseline screenshot of any page. QAProof re-checks it on your schedule (daily, weekly or monthly) and emails you when the score drops below your threshold. Catch broken deploys in hours, not weeks.
Design Audit (Design Debt Score)
How consistent is your design system — really?
The situation: “Our site uses 47 shades of gray and 12 different font sizes. There’s a design system, but nobody follows it. And we have no way to measure how bad it’s gotten.”
What you get: QAProof reads your live design tokens directly from the DOM — colors, fonts, spacing, CSS variables — and grades your design system’s internal consistency on a score from 0 to 100. 0 is ideal. See exactly where the drift started.
Who uses QAProof?
QAProof works equally well for non-technical site owners and experienced development teams.
- Agencies & studios — audit a client site in minutes instead of an afternoon, and hand over a PDF that names the WCAG criterion and the element for each finding.
- Public-sector sites — councils, schools and agencies working to EN 301 549, the European Accessibility Act or AgID: find what is findable automatically, then put your manual testing time where it counts.
- Freelancers — prove your work matches the design with objective data. A score is more convincing than “trust me.”
- In-house teams — set up monitors on your key pages and get alerted the moment a deploy breaks something.
- WordPress site owners — no code, no complexity. Install the plugin and click one button.
- QA engineers — help identify, reproduce, and investigate issues quickly, making the development process faster and more reliable.
- Designers — see exactly where your design was implemented incorrectly, and hand developers the precise CSS they need to fix it.
Getting started
Your first check needs nothing but the plugin:
- Install and activate QAProof.
- Open the QAProof menu and click Check my site.
- A real WCAG 2.1 AA check of your home page runs — usually 1–2 minutes — and you get a score and the issues found.
To go further, connect a free account (Settings → it takes a minute) and you can:
- audit any page, not just the home page, and pick WCAG Level A, AA or AAA;
- see every issue rather than the first few, each with its element and a recommendation;
- export a PDF or email the report;
- set a monitor that re-checks a page on a schedule and tells you when the score drops;
- run the visual tests below.
What you get in every report
- An overall quality score from 0 to 100 — clear, communicable, and objective.
- Category-by-category breakdown with visual charts.
- Every issue listed with its exact location on the page.
- Ready-to-paste CSS fix recommendations — not “something looks off” but “add margin-top: 16px to .header-nav”.
- PDF reports — the findings, the elements and the measured values, ready to send to your client in one click.
- Email reports — send directly from the interface without downloading.
- WCAG level selector (A / AA / AAA) — adjust audit strictness to match your requirements.
- Saved designs — save a Figma design once, reuse it across all future tests.
Why choose QAProof over separate tools?
The market has tools for design comparison. Separate tools for regression. Separate tools for accessibility. QAProof combines all five in one platform.
- WCAG 2.1 accessibility audit — Level A, AA, AAA
- A real result before you create an account
- Design vs. live page comparison
- Figma tool support
- Responsive testing across 5 viewports
- Visual regression monitoring
- Design Debt Score
- WordPress plugin with built-in admin UI
- Scheduled automatic monitoring
- PDF reports
- AI-generated CSS fix recommendations
Start for free today
Install the plugin and click Check my site. You will know where your site stands before you have typed an email address.
Installation
- Install the plugin from the WordPress plugin directory (or upload the ZIP via Plugins → Add New → Upload).
- Activate it — a QAProof menu appears in your admin sidebar.
- Open QAProof and click Check my site. Your accessibility score and the issues found appear in a minute or two. No account needed for this.
To audit other pages, see every issue, export PDFs or set up monitoring:
- Create a free account at qaproof.io/signup and copy your API key (API Keys page).
- Paste it into QAProof → Settings and save.
Frequently asked questions
Do I need an account?
Not for the first check. Install the plugin, click Check my site, and you get a real score and the issues found on your home page — no account, no API key, no card. An account (free) is what unlocks auditing other pages, seeing every issue rather than the first few, PDF export and scheduled monitoring.
Is QAProof free?
The WordPress plugin is free and open-source (GPL-2.0+). The first check of your site needs no account at all. The QAProof service then has a Free plan: 10 AI generations as a one-time trial — they do not reset monthly — 1 monitor, and 7 days of test history. If you sign up with an email address you get 3 of those 10 until you verify the address; signing in with Google or GitHub gives you all 10 immediately. Paid plans (Pro, Business, Scale) add more generations, monitors and history. Full pricing at qaproof.io/pricing.
Is this an accessibility overlay or a toolbar?
No. QAProof adds nothing to your pages and your visitors never see it. Overlays and toolbars try to patch a site from the outside at page load; they are widely rejected by disabled users and by accessibility professionals, and in 2025 the US Federal Trade Commission fined one overlay vendor $1,000,000 over claims about what its script achieved. QAProof does the opposite job. It reads your page, tells you which WCAG success criterion each defect relates to and which element is at fault, and then gets out of the way so the problem can be fixed in your theme or content — where it actually lives.
Does this make my site legally compliant?
No, and no automated tool can. It finds the problems that can be detected automatically — a large and useful share of them — but judging whether alt text is meaningful, whether the tab order makes sense, or whether someone using a screen reader can finish a purchase needs a person. EN 301 549, the European Accessibility Act, Section 508 and AgID all expect manual testing alongside automated checks.
Do I need a Figma account?
Only for Design Fidelity (Figma vs live page). Responsive, Accessibility, Design Audit and Visual Regression need just a URL.
What information does QAProof send when I run a test?
Only what you explicitly submit: the URL of the page you want to test and, for Design Fidelity, the Figma design link. QAProof never reads your post content, user accounts, visitor data, passwords, or any other information from your site. Every request also carries a normal User-Agent identifying the plugin version and your WordPress and PHP versions — the same thing any HTTP client sends — so we can tell which versions are in use when something breaks. Emailed reports carry the address you send them to, and the feedback form carries your WordPress user ID and your site’s home URL so we can…
Where are my test results stored?
Results are stored securely in your QAProof account, scoped to your workspace. The plugin itself stores only your settings (API key, saved designs as name + Figma link, notification and test preferences). Test results are not saved to your WordPress database.
How long does a test take?
Most tests finish in a few minutes (typically 1–5). Design Fidelity: 1–3 minutes. Responsive Testing: 2–4 minutes (5 viewports). Accessibility Audit: 2–5 minutes. Design Audit: 1–3 minutes.
Does the plugin work on WordPress Multisite?
Yes. The plugin can be network-activated, and each site in the network manages its own settings and API key independently. Note that test history lives in the QAProof account behind the API key — sites that share one API key share one test history.
What happens if I enter a wrong API key?
The API rejects it and the plugin shows an error; no test runs until you enter a valid key. You can update your key at any time.
Changelog
1.0.45
- Site Audit now starts with the pages in your menu. When a site has more pages than your plan audits in one run, the pages were chosen by the shape of their addresses, which on WordPress’s default permalinks came out as the first few posts in alphabetical order. The site’s own navigation is read first now, so the audit covers the pages you consider your main ones. This runs on the QAProof service and reaches you with or without this update. A site you have audited before keeps its page list, so results stay comparable.
- When an audit stopped at your plan’s limit, the report says so. It shows how many pages were found, how many were checked, and which plan covers more, with a link. It appears only when the limit was actually reached.
- A contrast ratio just under the requirement is no longer displayed as the requirement itself: 4.4957:1 was shown as “4.5:1 (needs 4.5:1)”. It is shown as 4.49:1.
1.0.44
- Findings that are not failures are now labelled Observation. Some items in a report are deliberately left out of the counts and the score: either WCAG does not require them (heading order, landmarks, duplicate ids) or the checker could not confirm them (text over a gradient). They were labelled Unverified, which only described the second kind.
- Fewer false failures, and fewer missed ones. The checks run on the QAProof service, so these reach you with or without this update. A skip link written as a button, an inactive tab, a focusable carousel slide and an SVG hidden from screen readers are no longer reported as Level A failures. Target size (WCAG 2.2) now applies its inline and spacing exceptions. Contrast is measured on the colour the text is actually drawn in, and large text uses the WCAG thresholds of 18pt, or 14pt bold. Focusable elements hidden from screen readers with aria-hidden are now reported.
- Monitors no longer report a hover colour as a change. The capture left the pointer in the middle of the page, so whatever sat under it could be photographed in its hover state and compared with a baseline taken without it.
- A grouped Site Audit finding now counts each page once. Two findings on the same page were shown as two pages.
1.0.43
- Reports no longer name CSS classes your page does not have. To photograph a page in its final state the audit marks lazy-loaded images, animations and collapsed menus as loaded, and those marker classes were leaking into the selectors in your report — so a finding could point at
img.img-fluid.lazyloaded, an element nowhere in your HTML. Runtime state such as the active carousel slide is left out too, which also stops one defect being listed several times depending on which slide happened to be showing. - The package no longer carries a second copy of Chart.js. Chart.js v4 publishes only minified builds, so the 208 KB
chart.umd.jsshipped next to the file the plugin loads was a duplicate that was never loaded. THIRD-PARTY-NOTICES.txt now says exactly what is bundled.
1.0.42
- Settings no longer says “This site is connected to your QAProof account” when the saved key is one the API rejects. It says a key is saved, and lets the account panel — which actually asks the API — report whether it works.
1.0.41
- Added the GPL-2.0 LICENSE file that THIRD-PARTY-NOTICES.txt has been telling you to read. The build now refuses to package without it.
- Category names in the report now describe what is actually in them: an invalid ARIA role was filed under “Spacing & Layout” and a broken page language under “Text Readability”.
1.0.40
- A mistyped API key now tells you so. Settings queued an error and never printed it, so pasting a malformed key returned a page that silently did nothing. Saving correctly says so now too.
- The PDF no longer carries a “verified” seal. Nothing verified it — there was no signature and nothing a recipient could check. It says what it is: an automated check. This plugin’s own FAQ tells you to be sceptical of exactly that kind of mark, and it should hold itself to that.
- The readme now matches the code on what leaves your site (the plugin version and your WordPress and PHP versions travel in the User-Agent, as with any HTTP client), on Site Audit’s per-plan page limit, and on the fact that a finished site audit emails you a copy.
- Fixed a finding that contradicted itself on a default WordPress theme, reporting content “outside any landmark region” while listing the landmarks it was inside.
- Errors from the analysis service are now written for you rather than for whoever operates it.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Accessibility Checker alternatives
All a11y plugins →
FAQ
Accessibility Checker: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 4, 2026
Is Accessibility Checker free?
Yes. Accessibility Checker is free to download and use from the official WordPress.org plugin directory.
Is Accessibility Checker safe to use in 2026?
Accessibility Checker is a solid plugin choice in 2026, with a few things worth checking first. Is rated 5/5 and was last updated 3 days ago, and scores 71/100 on our health check.
How many websites use Accessibility Checker?
Accessibility Checker is active on <10 WordPress websites and has been downloaded 805 times since it launched in May 2026. It was downloaded 345 times in the last 30 days.
Does Accessibility Checker work with WordPress 7.1?
Yes. The developer has tested Accessibility Checker up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Accessibility Checker need?
Accessibility Checker requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Accessibility Checker last updated?
The latest version, 1.0.45, was released on October 1, 2026 (3 days ago).
Who makes Accessibility Checker?
Accessibility Checker is developed and maintained by QaProof.
What are the best alternatives to Accessibility Checker?
The most popular alternatives to Accessibility Checker are Web Accessibility (formally… (500K+ installs), WP Accessibility (60K+ installs) and AccessibleWP (20K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
