VPATs and Accessibility Statements
Produce the documents procurement and law expect.
VPATs and Accessibility Statements is a free Web Accessibility Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Accessibility Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Two Documents, Two Jobs
A VPAT serves buyers in procurement, while an accessibility statement speaks to everyday users. Many organizations need both.
What VPAT Stands For
VPAT means Voluntary Product Accessibility Template, a standard form a vendor fills in to describe how a product meets accessibility criteria.
It Produces an ACR
A completed VPAT yields an Accessibility Conformance Report, the actual document a buyer reviews before purchasing your software.
The Three Verdicts
For each criterion the report says Supports, Partially Supports, or Does Not Support, plus remarks explaining the real-world detail.
Pick the Right Edition
VPAT editions map to standards: choose the WCAG edition, or the combined one if you also need Section 508 and EN 301 549 columns.
Driven by Procurement
Government and large enterprise buyers often require a VPAT before they will even consider a product, especially in the U.S. and EU.
Honesty Protects You
An inflated VPAT can become evidence against you. Marking something Supports when it does not is a liability, so be precise and truthful.
Now the Public Statement
An accessibility statement is the user-facing page describing your conformance target, known issues, and how to report a barrier.
What It Should Contain
Name the standard and level you target, list known limitations, give a contact channel, and date the page so readers know it is current.
Required by Some Laws
In the EU public sector and elsewhere, a published accessibility statement with feedback contact is not optional but legally mandated.
Keep Both Alive
A stale VPAT or statement is worse than none, so re-audit after major releases and update both so they keep matching reality.
Quick Check
Recall the difference between the two documents.
Recap: VPATs and Statements
A VPAT produces an ACR for buyers, and an accessibility statement informs users. Keep both honest, dated, and current. Course complete! 🎯
Frequently asked questions
Is the “VPATs and Accessibility Statements” lesson free?
Yes — the full text of “VPATs and Accessibility Statements” is free to read here on the web, and the Web Accessibility Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Accessibility Academy course, upgrade to CoddyKit PRO.
What will I learn in “VPATs and Accessibility Statements”?
Produce the documents procurement and law expect. You practise Web Accessibility Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Web Accessibility Academy?
No prior experience is required. Web Accessibility Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “VPATs and Accessibility Statements” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Web Accessibility Academy lesson?
Yes. Every Web Accessibility Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- ADA, Section 508, and US Web Lawsuits
- The European Accessibility Act and EN 301 549
- WCAG as the Common Legal Yardstick
- VPATs and Accessibility Statements