A Definition of Done That Includes a11y
Make accessibility a release requirement.
A Definition of Done That Includes a11y is a free Web Accessibility Academy lesson on CoddyKit — lesson 2 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 Done Really Means
A Definition of Done is the shared list a team agrees a feature must meet before anyone calls it finished. ✅
Done Is Not Just Working
A feature that works for a mouse user is not done if a keyboard or screen reader user cannot use it at all.
Make a11y Non-Optional
Put accessibility in the Definition of Done so it becomes a requirement to ship, not a nice-to-have someone can quietly drop.
Keyboard Pass
One done item: every interactive element is reachable and operable by keyboard alone, with no part of the feature mouse-only.
Visible Focus Pass
Another item: focus is always visible as you tab, so a keyboard user never loses track of where they are on the page.
Names and Labels Pass
Done also means every control has an accessible name, so a screen reader announces what each button or input actually does.
Automated Scan Pass
Add a quick axe or Lighthouse scan to the list. It will not catch everything, but it stops obvious regressions cheaply.
Put It in the Template
Bake the items into your ticket or pull request template as a checklist, so no one has to remember them from memory.
## Definition of Done
- [ ] Keyboard reachable
- [ ] Visible focus
- [ ] Controls have names
- [ ] axe scan cleanReviewers Enforce It
In code review, reviewers check the accessibility boxes too. A reviewer who blocks an unlabeled button keeps the bar high.
Start Small and Grow
Begin with a few high-impact items your team can actually meet. A short list people follow beats a long one they ignore.
Prevent, Do Not Patch
A good Definition of Done turns accessibility from a later patch into something built in from the start of every feature.
Quick Check
Why add accessibility to your Definition of Done?
Recap
A Definition of Done with accessibility items, like keyboard, focus, names, and a scan, makes a11y a requirement to ship every feature. ✅
Frequently asked questions
Is the “A Definition of Done That Includes a11y” lesson free?
Yes — the full text of “A Definition of Done That Includes a11y” 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 “A Definition of Done That Includes a11y”?
Make accessibility a release requirement. 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 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “A Definition of Done That Includes a11y” 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
- Shift Left: a11y in Design and Tickets
- A Definition of Done That Includes a11y
- A Practical Per-Feature Accessibility Checklist
- Champions, Training, and Lasting Change