Accessibility Checker – WCAG 2.1 AA, EAA & Section 508 Site Audit – QAProof

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: none and 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 lang attribute, 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.