WCAG certification for a website: what an accessibility statement proves


There is no official WCAG certification for websites, and no EU law requires one. A client who asks a small business for a WCAG certificate actually gets a page where the business lists its own site's problems: its accessibility statement. It can follow a standard template and should rest on an audit, in-house or external. Before publishing, it pays to check that the audit backs it, then to send both.
From the delivered page to the reply to a client
#What is an accessibility statement, and who certifies it?
An accessibility statement is the page where an organization declares how accessible its own site is. The EU publishes a model statement, the template its public bodies must follow. Under that model, the claims must be accurate and rest on an actual evaluation: a self-assessment, or an assessment by a third party, such as a certification. EU countries may also accept other measures that are just as reliable. Either way, the claims are the organization's own.
It serves, for example, people who navigate by keyboard because they can't use a mouse, and people who control their computer by voice through software that acts as a keyboard. The page tells them what doesn't work yet, the alternative when there is one, and how to report a problem.
Before listing problems, the statement gives a compliance status, and the EU model sets what each status means. Each one reports what an evaluation found, so a site nobody has evaluated can claim none of them. For that case, the W3C, which writes the web's accessibility guidelines, adds a fourth status to its statement generator: "Not assessed."
| Status | What the evaluation found |
|---|---|
| Fully compliant | Every requirement met, with no exceptions |
| Partially compliant | Most requirements met, with some exceptions |
| Not compliant | Most requirements not met |
| Not assessed (W3C generator) | No evaluation, or no results available |
#Who has to publish one?
EU law requires a statement from public sector bodies, under the Web Accessibility Directive. A business that sells online to consumers is covered by the European Accessibility Act. The Act asks it for an accessible site, and for information on its accessibility in its terms and conditions or an equivalent document. Microenterprises are exempt: fewer than 10 employees, and €2 million or less in annual turnover or balance sheet total.
Creek House, a caterer with 40 employees, sells nothing to consumers, so neither law applies to it. Its agency delivers a redesigned site whose Accessibility page claims full compliance. The week the site goes live, a buyer at one of its clients asks for "a WCAG certificate" before renewing the contract. Publishing the page is optional, but its words, "fully compliant" included, keep the meaning the EU model and the W3C give them.
Marker 1. The status shown at the top of the page: “Accessibility: fully compliant”. Marker 2. The line “Automated scan of the home page, November 2, 2026,” scored 100/100. Marker 3. The Non-compliance subsection, which says “None.”.#How to check an accessibility statement against the site it describes?
Before publishing, check three things: where the status comes from (who evaluated, and which pages), the list of problems, and the contact option.
#Does the status come from an audit, and of which pages?
An audit sets the status by checking the site's pages against WCAG, the W3C's accessibility guidelines. The W3C's evaluation method recommends evaluating every page when that's feasible, as on a site of a few pages. A larger site gets a sample. It covers the main pages, linked from the home page, menu or footer, each page type and essential function, every step of a process, and a few random pages.
The Creek House site has nine pages, so an audit checks all nine. The automated scan cited on its Accessibility page read only one. The W3C warns that such a tool can't judge a site's accessibility on its own, since some checks take human judgment.
The EU model then asks for the date the statement was prepared and the method, such as a self-assessment or an assessment by a third party. That date is when the statement was written or updated, after an evaluation. The model has no field for the audit's date. On the delivered page, those lines say "automated online checker" and November 2, 2026, the day of the scan. The agency also listed the pages checked: "Home page." Nothing there supports "fully compliant."
#Are the site's problems listed, with an alternative?
The Non-accessible content section lists what doesn't work yet, with an accessible alternative where there is one. The EU model's own example of a problem is a login form that is "not fully usable by keyboard."
The delivered page says "None." To check, we went through the quote form with Tab, following the focus, the outline that shows where the keyboard is.
After the logo and the five menu links, the seventh press reaches “Company.”
Six presses later, the focus enters “Your message,” the last field.
The next press skips “Send my request” and lands on “Legal notice,” in the footer.
Shift+Tab goes back to the field: the button is never reached.
A keyboard user fills in all seven fields and can't send anything. The agency built the button as a block that only reacts to a click, and Tab passes it by. WCAG asks for everything on a page to work from a keyboard, at level A, its lowest level. A page that misses even one level A rule can't conform, so this one button fails the quote page and any claim of full compliance. The European standard EN 301 549 includes the same rule.
The button therefore goes under Non-accessible content, with quotes requested by phone or email until it's fixed. On your own form, the test takes a minute: from the last field, press Tab and see whether the focus lands on the submit button.
#Does the contact option work with a keyboard?
The statement offers an accessible way to report a problem or ask for content in another format: an email address or a web form, for example. The W3C advises offering more than one. In the EU model for public bodies, the statement also links to its country's enforcement procedure, the way to complain when a report or request gets no satisfactory answer.
At Creek House, the contact line sends people to the quote form and its unreachable button. A keyboard user blocked there can neither request a quote nor report the problem. An email address gives them both.
Avoid
Marker 1. The contact block, which points to “our contact form”.Correct
Marker 1. The contact block, which gives the address accessibility@creekhouse.example.#What changes on the corrected page?
On the corrected Creek House page, a keyboard user finally finds, under Non-accessible content, how to send a request. At the top, though, the status now reads "Accessibility: not assessed" until the audit planned for January 2027. With no evaluation behind it, the page can claim none of the EU model's three statuses.
The caterer asks its agency to fix the button and to change the status everywhere it appears, footer link included. This page is a stopgap until the audit, since the EU model wants a statement's claims to rest on an actual evaluation or an equivalent measure. To fill in the model section by section, follow our guide.
Website accessibility statement: from the audit report to a published page
#What to send a client who asks for a WCAG certificate?
No EU law requires a certificate for a website, so send the statement with the audit report. The W3C says statements "are not technical assessments or declarations of conformity," and that ideally they point to one, such as an audit report. The EU model suggests linking to the evaluation report, especially when the status reads "fully compliant," so your client can open it in one click. With no audit yet, give the planned date.
Your reply gives the statement's link and status, then the audit: date, auditor, pages, and the report attached or to follow.
Marker 1. The status shown at the top of the page: “Accessibility: not assessed”. Marker 2. The Non-compliance subsection: the “Send my request” button out of keyboard reach, and quotes by phone or email. Marker 3. “This statement was prepared on November 6, 2026,” then the audit of the nine pages planned for January 2027.Creek House therefore sends the buyer who wanted a certificate its "not assessed" page. It's the caterer's own word. The buyer can check its one listed problem in a minute: on the quote form, from "Your message," a single press of Tab skips the button.
Website accessibility audit: cost, quotes and how to choose an auditor
To replace the home page scan with a real result, Includdy runs accessibility audits whose report gives the status to declare and the non-compliances to list in the statement. For each non-compliance its scan finds, it also generates a test plan, with steps and expected results, that the whole team can replay after a fix.


