Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 38 ยท Legal, Process and Culture

Building Accessibility into Your Process

Make accessibility part of design, development, QA and procurement: shift left, definition of done, component libraries, training, user testing and measuring progress.

Teams that treat accessibility as a final audit pay for it three times: once to build the wrong thing, once to find the problem, and once to rebuild it. Fixing a missing label in a design file costs minutes; fixing it in a live product with hundreds of screens can cost weeks. The solution is to shift left: bring accessibility into every stage, starting at the first sketch.

Why it is cheaper early

flowchart LR
  A["Research and design"] --> B["Build"]
  B --> C["Test"]
  C --> D["Release"]
  D --> E["Maintain"]
  A -. "cheapest to fix" .-> A
  D -. "most expensive to fix" .-> D

The same issue costs more at each step to the right.

Roles and responsibilities

Everybody owns a piece.

Role Accessibility duties
Product owner Writes accessibility into requirements and acceptance criteria; budgets time.
Designer Checks contrast and target size in the design, specifies focus states, headings and labels, annotates reading order.
Content author Plain language, descriptive headings and links, alt text, captions and transcripts.
Developer Semantic HTML first, ARIA only where needed, keyboard support, linting and tests.
QA Manual keyboard and screen reader tests, regression checks on key flows.
Leadership Sets policy, funds training, tracks metrics and removes blockers.

A named accessibility champion per team helps, but a champion is a coach, not a gatekeeper who does all the work.

Put it in the definition of done

Add checks to your existing agile ritual. A feature is not done until:

  • It can be used with the keyboard only, with visible focus.
  • Headings, landmarks and labels are correct.
  • Contrast and target size pass.
  • Automated checks (axe, linters) are green in CI.
  • A quick screen reader pass was done on new interactive parts.
  • Content has alt text, captions and meaningful link text.

Write accessibility acceptance criteria into stories: "Given a keyboard user, when they open the filter panel, then focus moves to the first control, Escape closes it and focus returns to the Filters button."

Definition-of-done checklist

Design systems and components

The best leverage is a shared component library that is accessible by default. Fix a dialog once and every product that uses it improves. Practical advice:

  • Build components on native elements first.
  • Document keyboard behavior, ARIA, focus and content rules for each component.
  • Include accessibility tests in the component's own test suite.
  • Provide accessible design tokens: color pairs tested for contrast, focus ring styles, spacing for target sizes.
  • Treat a11y bugs in a shared component as high priority.

Training and culture

  • Give every role a short, role-specific course, then refresh it yearly.
  • Run empathy sessions: let teammates try the product with only a keyboard, a screen reader or with the screen zoomed 400%.
  • Share real stories and user feedback.
  • Celebrate fixes in the same way you celebrate features.
  • Avoid shame. Blame stops people reporting problems.

Involve disabled people

Standards cannot cover every real-world barrier. Include disabled people in research and usability testing, paying them fairly for their time, and hire them where you can. Recruit people who use a variety of assistive technologies. Prototype tests with a few participants uncover problems that audits miss, like confusing wording or exhausting flows.

Accessibility in procurement and third parties

Your site is only as accessible as its weakest dependency: payment widgets, chat plug-ins, cookie banners, maps, embedded video players. Ask vendors for an ACR, test the demo before you buy, and put accessibility terms in the contract. Track third-party issues in your statement.

Measure progress

Pick a few metrics and look at trends rather than perfection:

  • Number of open accessibility issues by severity.
  • Percentage of key journeys passing manual checks.
  • Time to fix issues.
  • Automated violation count in CI over time.
  • Training completion and satisfaction scores from users.

A simple maturity model helps leaders see where to go: ad hoc (we fix when sued), reactive (we audit and fix), proactive (we test during development), embedded (accessibility is in every process and measured).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does 'shift left' mean for accessibility?

    The earlier a problem is caught, the cheaper it is to fix.
  2. 2. Which is the best place to put accessibility checks so they are not forgotten?

    Putting checks in the definition of done and automating them in CI makes them part of normal work.
  3. 3. Why invest in an accessible component library?

    Reuse spreads fixes widely, but components still need testing in context.
  4. 4. Which method finds issues that audits often miss?

    Real users reveal confusing wording and exhausting flows that standards checks do not capture.

Summary

  • Shift left: include accessibility in research, design, content, code, QA and procurement.
  • Add accessibility to the definition of done and to CI; write accessibility acceptance criteria.
  • Build and document accessible components and design tokens.
  • Train people, involve disabled users, and measure progress over time.

Next: Project: Fix a Broken Page