Определение готовности, включающее доступность

A Definition of Done is the shared list a team agrees a feature must meet before anyone calls it finished. ✅

A feature that works for a mouse user is not done if a keyboard or screen reader user cannot use it at all.

Put accessibility in the Definition of Done so it becomes a requirement to ship, not a nice-to-have someone can quietly drop.

One done item: every interactive element is reachable and operable by keyboard alone, with no part of the feature mouse-only.

Another item: focus is always visible as you tab, so a keyboard user never loses track of where they are on the page.

Done also means every control has an accessible name, so a screen reader announces what each button or input actually does.

Add a quick axe or Lighthouse scan to the list. It will not catch everything, but it stops obvious regressions cheaply.

Bake the items into your ticket or pull request template as a checklist, so no one has to remember them from memory.

In code review, reviewers check the accessibility boxes too. A reviewer who blocks an unlabeled button keeps the bar high.

Begin with a few high-impact items your team can actually meet. A short list people follow beats a long one they ignore.

A good Definition of Done turns accessibility from a later patch into something built in from the start of every feature.

Why add accessibility to your Definition of Done?

A Definition of Done with accessibility items, like keyboard, focus, names, and a scan, makes a11y a requirement to ship every feature. ✅