Process

Building an Accessibility Champions Program

By EZUD Published · Updated

Building an Accessibility Champions Program

An accessibility champions program distributes accessibility expertise and advocacy across the organization. Rather than concentrating all accessibility responsibility in a single specialist or small team, champions embed accessibility knowledge into every product team, design group, and content function. This model scales accessibility practice far beyond what a centralized team can achieve alone.

What Champions Do

Accessibility champions are not full-time accessibility specialists. They are designers, developers, QA engineers, product managers, or content creators who dedicate a portion of their time to accessibility within their team. Typical responsibilities include:

  • First responder. Answer accessibility questions from teammates before escalating to the central accessibility team.
  • Reviewer. Participate in design reviews and code reviews with an accessibility lens.
  • Advocate. Raise accessibility considerations during sprint planning, backlog refinement, and retrospectives (see accessibility in agile workflows).
  • Tester. Conduct basic manual accessibility testing (keyboard navigation, quick screen reader checks) on new features.
  • Connector. Relay standards, tools, and best practices from the central accessibility team to their product team.
  • Feedback channel. Report accessibility gaps, tool needs, and process improvements back to the central team.

Organizational Model

The champions program works best as the “spoke” in a hub-and-spoke model:

  • Hub: A central accessibility team or program manager who sets standards, provides training, maintains the governance framework, and coordinates the program.
  • Spokes: Champions embedded in product teams who apply standards, conduct reviews, and advocate locally.

This model is the most common pattern in organizations that have achieved sustained accessibility maturity. See hiring accessibility specialists for how the hub team is structured.

Launching the Program

Recruit volunteers

Champions should be volunteers, not conscripts. People who are genuinely interested in accessibility are more effective advocates than people who are assigned the role. Recruit through internal communications, accessibility awareness events, and manager recommendations.

Aim for at least one champion per product team. In larger organizations, aim for one per team of 8-12 people.

Provide training

Champions need deeper training than the general population. A typical curriculum includes:

  • WCAG 2.2 Level AA fundamentals
  • Hands-on screen reader testing (NVDA, VoiceOver)
  • Keyboard testing methodology
  • Using automated tools (axe DevTools, Accessibility Insights)
  • Design review and code review for accessibility
  • How to read and evaluate a VPAT/ACR

This builds on the general training provided to all developers, designers, and content creators.

Allocate time

Champions need dedicated time for accessibility work. If the role is entirely on top of existing responsibilities, it will be deprioritized when deadlines tighten. Work with managers to allocate 10-20% of the champion’s time to accessibility activities. This allocation should be reflected in performance expectations.

Build community

Regular champion meetings (biweekly or monthly) create a community of practice where champions:

  • Share challenges and solutions from their teams
  • Learn about new tools, standards, and organizational updates
  • Practice skills (group screen reader testing sessions, design review exercises)
  • Support each other through the sometimes-frustrating work of advocacy

Sustaining the Program

Recognition

Acknowledge champions’ contributions publicly. Highlight their work in company communications, include accessibility contributions in performance reviews, and consider formal recognition (awards, conference attendance sponsorship).

Career development

Position the champion role as career development, not extra work. Champions build expertise that is increasingly valued in the industry. Support champions who want to pursue IAAP certification or transition into dedicated accessibility roles.

Rotate and refresh

Allow champions to rotate out after a defined term (12-18 months) and recruit new ones. This prevents burnout and spreads accessibility knowledge to more people over time. Outgoing champions retain their skills and continue to contribute informally.

Measure impact

Track champion program metrics:

  • Number of accessibility issues caught in team-level reviews (before they reach the central team)
  • Team-level automated scan pass rates
  • Accessibility training completion rates in champion-supported teams versus non-champion teams
  • Champion satisfaction and retention surveys

Report these metrics through accessibility dashboards.

Common Pitfalls

  • No time allocation. Champions who must do accessibility on top of a full workload burn out quickly.
  • No training. Enthusiastic but untrained champions may provide incorrect guidance.
  • No central support. Champions without a hub team to set standards and answer complex questions feel isolated and unsupported.
  • No recognition. Champions who feel their work is invisible will stop doing it.

Key Takeaways

  • Champions distribute accessibility expertise across the organization as part of a hub-and-spoke model.
  • Recruit volunteers, provide deep training, allocate dedicated time, and build a community of practice.
  • Recognize contributions in performance reviews and company communications.
  • Allow rotation to prevent burnout and spread knowledge to more people over time.
  • Measure champion impact through review catch rates, scan pass rates, and training completion in their teams.

Sources

More in Process

Inclusive Design Process Guide: Building Accessibility Into Every Stage Guide Continuous Accessibility Monitoring Accessibility in Design Reviews Nothing About Us Without Us: The Principle That Shapes Inclusive Design

View all Process articles →