Writing a Defensible Conformance Statement
Document what you meet and where you fall short.
Writing a Defensible Conformance Statement 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.
What a Statement Is
A conformance statement publicly records which WCAG version and level your site meets, and where it currently falls short.
Honesty Is the Point
The goal is not to claim perfection. An honest, specific statement builds trust and is far more defensible than a vague all-green badge.
Name the Standard
State the exact target, for example WCAG 2.2 Level AA. A reader should never have to guess which version or tier you measured against.
List the Scope
Define what was evaluated: which pages, flows, and dates. A statement that covers the whole site but only tested one page is not credible.
Record Known Gaps
Spell out the criteria you do not yet meet and why. Naming known issues with a remediation timeline shows a real, ongoing commitment.
Cite Your Methods
Note the tools and tech you used, like axe, NVDA, and Chrome. This is the evidence that turns a claim into a tested result.
Add Contact and Feedback
Give users a way to report barriers. A clear feedback channel is both good practice and required by several accessibility laws.
VPAT and the ACR
For procurement, a VPAT produces an Accessibility Conformance Report mapping each criterion to Supports, Partially Supports, or Does Not Support.
Be Precise, Not Promotional
Avoid words like fully accessible. Say which criteria are met and which are partial. Overclaiming is exactly what invites legal challenge.
Keep It Current
A statement has a date and goes stale fast. Re-audit after major releases and update the document so it always reflects reality.
Where to Publish It
Link your accessibility statement from the footer of every page, so anyone, including auditors, can find it in one predictable place.
Quick Check
Identify what makes a conformance statement defensible.
Recap: Conformance Statements
State the exact target, scope, methods, and known gaps, keep it dated and linked, and never overclaim. That is what holds up. Course complete! 🎯
Frequently asked questions
Is the “Writing a Defensible Conformance Statement” lesson free?
Yes — the full text of “Writing a Defensible Conformance Statement” 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 “Writing a Defensible Conformance Statement”?
Document what you meet and where you fall short. 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 “Writing a Defensible Conformance Statement” 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
- A, AA, AAA: Picking the Right Target
- The 2.2 Additions: Focus Appearance & Target Size
- Dragging Movements and Accessible Authentication
- Writing a Defensible Conformance Statement