WCAG Certification: What It Is, What It Isn't, and How to Get One for a WordPress Site

There Is No Official WCAG Certification

The Web Content Accessibility Guidelines are published by the World Wide Web Consortium. The W3C defines what it means to conform, and it defines what a conformance claim must contain. It does not test websites, and it does not issue certificates. Its own guidance on conformance says so in one line: "It is not required to make any conformance claim in order to conform." A claim, when one is made, is something the site owner writes about their own site.

That leaves two honest kinds of "WCAG certification" in the world. The first certifies people: the International Association of Accessibility Professionals runs exams (CPACC, WAS, and the combined CPWA) that say a person knows the standard. The second is a document about a site, and every one of those is issued by a private company, on that company's terms. A certificate from a vendor is that vendor's statement of what it tested. Nothing more, and, if it is written honestly, nothing less.

The Four Documents People Mean by "Certification"

1. A conformance claim

This is the W3C's own format. Per the Understanding Conformance document, a claim states the date, the exact pages or URI scope covered, the WCAG version and level, and the technologies relied upon. Its example reads: "On 20 September 2009, all web pages at http://www.example.com conform to Web Content Accessibility Guidelines 2.0 … Level A conformance." Note what it is: a dated, scoped statement made by the site owner. It is not reviewed by anyone at the W3C.

2. An audit report

An audit is the work behind any claim. A tester, a tool, or both go through pages against the success criteria and record what passed, what failed, and what could not be determined. A good audit report tells you the sample of pages, the method (screen reader, keyboard, automated tool, or all three), the standard and level, and the date. The word "audit" is doing real work when a human tested with assistive technology, and much less work when it describes a single automated crawl.

3. A VPAT / ACR

The Voluntary Product Accessibility Template is a free template from the Information Technology Industry Council. Per ITI, it "translates accessibility requirements and standards … into actionable testing criteria for products and services," and "a version of the VPAT which has been completed for a specific product is an ACR," an Accessibility Conformance Report. The current template is version 2.5Rev, dated April 2025. This is what government and large enterprise buyers ask software vendors for. If you run a WordPress site for a bakery, nobody will ask you for one.

4. A vendor certificate

This is what most people picture: a one-page PDF with a score and a date. It is a summary of an audit, produced by whoever ran the audit. It can be a useful piece of paper or a meaningless one, depending entirely on what the audit covered. The section below is how to tell.

How to Read Any WCAG Certificate in 60 Seconds

Whoever issued it, look for five things. If one is missing, the certificate is decoration.

1. A date. Accessibility is a property of the site on a given day. A certificate with no date, or a "valid until" date a year out, is claiming something no test can support, because the site will change tomorrow.
2. A scope. Which pages, or how many. "The website" is not a scope. "Forty-one pages crawled from the home page" is.
3. A standard and a level. WCAG 2.1 AA is the level courts and demand letters point to. A certificate that says "WCAG compliant" without a version and level is not saying anything checkable.
4. A method. Automated, manual, or both. Automated-only is fine as long as the document says so and says what fraction of the standard that covers.
5. A count. Violations found, and if fixes are claimed, violations fixed. A certificate that reports a score but no counts hides the one number a lawyer will ask about.

One more test: does the document claim compliance, or document effort? Any certificate that says a site is ADA compliant is overreaching, because no tool or auditor can promise how a judge will read Title III. The honest version says what was tested and what was found.

What Automated Testing Can and Cannot Certify

Software can check the mechanical criteria: whether an image has alt text, whether a form field has a label, whether text contrast clears 4.5:1, whether headings skip levels, whether a button has an accessible name. That set is large enough to matter. It is where the majority of real-world failures live, and it is what the Department of Justice lists first in its own web accessibility guidance: "the absence of alternate text, missing captions or transcripts for video and audio content, insufficient color contrast."

Software cannot check the judgment criteria: whether the alt text describes the image usefully, whether a caption is accurate, whether a page still makes sense with styles off, whether the reading order matches the visual order. Across the whole standard, roughly 30 to 40 percent of success criteria can be tested by a machine at all. That is why the same DOJ guidance recommends pairing an automated checker with manual testing.

So an automated certificate can honestly say: on this date, these pages were checked against these rules, and here is what was found. It cannot honestly say the site conforms to WCAG 2.1 AA in full. If a vendor's certificate says the second thing on the strength of a crawl, that is the overreach the FTC fined accessiBe $1 million for in 2025.

Getting a Certificate for a WordPress Site

WCAGpatch is a WordPress plugin, and its certificate is the automated kind, written to pass the 60-second test above. Here is exactly what is on it, checked against the plugin's own template on 2026-09-07.

• Website and site name, taken from your WordPress settings.
• Assessment date: the date of the latest scan. The PDF is regenerated after every scan, so it cannot go stale without you noticing.
• Pages scanned, as a count.
• Violations found and violations remediated, as counts. The remediated count reflects fixes the plugin applied on Pro and Agency, or that you marked fixed.
• WCAG 2.1 Level A or AA, whichever you set as the target.
• A site-wide score and grade (A at 90 and above, B at 75, C at 60, F below that).
• The disclaimer, printed on the certificate itself: generated by an automated tool, not legal advice, not a guarantee of full ADA or WCAG compliance, documents a good-faith effort.

The scan runs on every tier, including the free one. The certificate is available from Starter ($69, one time) and up. On Pro and Agency the scanner switches from the PHP checks to axe-core's 64 automated rules and adds the AI fixer, so the "remediated" count on the certificate starts to mean something. To see what your site would score before spending anything, run the free scan.

What a Certificate Does in a Demand-Letter Situation

It does not make the letter go away. Per law firm Saul Ewing's summary of the current litigation wave, more than 4,000 website accessibility suits were filed in 2024, and a business that does not resolve a complaint "can be forced to defend such cases, make their websites compliant, and pay significant attorneys' fees to the prevailing plaintiff."

What a dated certificate changes is the conversation. A site owner who can show a scan from three months before the letter, the violations it found, and the fixes applied since, is in a different position from one who cannot show anything. That documented effort is what the DOJ's guidance describes and what counsel will ask you for first. Keep every certificate the plugin generates; the history is the evidence, not the latest page. And talk to a lawyer before you answer any letter. This page is not that lawyer.

Sources

1. W3C, "Understanding Conformance," WCAG 2.1. Conformance claims are optional; required components of a claim (date, scope, version and level, technologies relied upon); example claim text quoted above.
2. ITI, "VPAT". Definition of the VPAT and the ACR, who completes it, current template version 2.5Rev (April 2025).
3. DOJ, "Guidance on Web Accessibility and the ADA". Common barriers list; recommendation to pair automated checkers with manual testing.
4. Saul Ewing LLP, "A Rise in ADA Website Accessibility Lawsuits". 4,000+ suits in 2024; consequences of an unresolved complaint; FTC order against accessiBe.
5. International Association of Accessibility Professionals. CPACC, WAS and CPWA are professional certifications for individuals, not for websites.
6. WCAGpatch product facts, checked 2026-09-07 against the plugin's certificate template and tier table: fields on the PDF, grade thresholds, certificate from Starter up, axe-core 4.11.1 with 64 automated rules on Pro and Agency, and the 30 to 40 percent automated-coverage disclaimer printed on every certificate.