Center of Excellence vs. Embedded Model: Designing Accessibility Governance That Scales

Accessibility governance determines whether accessibility happens consistently across an organization or remains dependent on individual team attention. Two dominant models have emerged: the Center of Excellence (CoE) with centralized expertise, and the embedded model with accessibility distributed across product teams.

Neither model is universally superior. The right choice depends on organizational culture, scale, technical architecture, and existing governance patterns. Many successful organizations use hybrid approaches, combining centralized standards with embedded execution.

This guide compares the CoE and embedded models, examines their strengths and weaknesses, and provides frameworks for designing accessibility governance that scales with your organization.

How Should You Organize for Accessibility?

The Governance Question

What is accessibility governance? Accessibility governance defines how an organization structures ownership, accountability, standards, and processes for accessibility across products and teams. It determines who sets policy, who executes, and who verifies compliance.

Organizations face core questions:

Ownership: Who is responsible for accessibility outcomes?

Standards: Who defines accessibility requirements and best practices?

Execution: Who implements accessibility in products?

Verification: Who ensures accessibility is actually achieved?

Escalation: What happens when teams ship inaccessible products?

Without clear governance, accessibility becomes optional—pursued by motivated individuals but absent from organizational expectation.

The Two Dominant Models

Center of Excellence (CoE): Centralized team of accessibility specialists who set standards, conduct audits, provide consultation, and ensure compliance.

Embedded Model: Accessibility expertise distributed across product teams, with each team responsible for their own accessibility outcomes.

Most organizations don't choose pure models but blend elements based on needs and constraints.

The Accessibility Center of Excellence Model

Strengths of Centralized Expertise

How does an accessibility Center of Excellence work? A CoE centralizes accessibility specialists who develop standards, provide training, conduct audits, consult on complex issues, and report on organizational accessibility status. Teams engage the CoE for expertise and validation.

Deep expertise concentration:

• Full-time accessibility specialists develop deep knowledge
• Specialists stay current on standards, techniques, and trends
• Complex issues get expert attention
• Career path for accessibility professionals

Consistent standards and practices:

• Single source of truth for requirements
• Consistent interpretation across teams
• Standardized testing methodologies
• Unified documentation and guidelines

Organizational visibility:

• Central team can report organization-wide status
• Single point of contact for executive inquiries
• Coordinated response to regulatory requirements
• Clear escalation path for issues

Training and enablement:

• Structured training programs
• Office hours and consultation availability
• Pattern libraries and documented solutions
• Mentorship for interested team members

Weaknesses of CoE Model

Potential bottlenecks:

• Teams wait for CoE reviews, slowing releases
• Limited CoE capacity constrains velocity
• Queue management becomes necessary
• "Throw it over the wall" dynamic

Distance from product decisions:

• CoE learns about features late in development
• Consultations occur after design decisions are made
• Retrofitting replaces building-in
• Recommendations may not consider team context

Dependency creation:

• Teams don't develop accessibility skills
• CoE absence means accessibility absence
• Knowledge remains concentrated, not distributed
• Teams feel absolved of responsibility

Scaling challenges:

• CoE must grow with organization (or bottleneck worsens)
• Expertise concentration limits reach
• Travel to distributed teams creates friction
• Timezone differences affect global organizations

The Embedded Model

Strengths of Distributed Ownership

How does embedded accessibility work? In the embedded model, each product team includes accessibility expertise—either dedicated accessibility roles or trained team members—with accountability for their own accessibility outcomes.

Proximity to decisions:

• Accessibility considered from project start
• Specialists participate in design discussions
• Implementation happens alongside feature development
• Context-aware recommendations

Scalability:

• Accessibility capacity grows with teams
• No central bottleneck
• Each team owns their velocity
• Parallel work across organization

Deep product knowledge:

• Embedded specialists understand their product thoroughly
• Know where bodies are buried
• Understand technical constraints
• Build relationships with team members

Ownership and accountability:

• Teams feel responsible for their accessibility
• No "someone else's job" mentality
• Direct accountability for outcomes
• Incentives align with team goals

Weaknesses of Embedded Model

Fragmentation risk:

• Different teams interpret standards differently
• Inconsistent user experience across products
• Wheel reinvention without shared learning
• Conflicting patterns and approaches

Uneven expertise:

• Some teams have skilled specialists, others don't
• Hiring accessibility talent is competitive
• Career progression unclear for embedded roles
• Knowledge gaps in some areas

Isolation and burnout:

• Embedded specialists may lack peer support
• Single points of failure when specialists leave
• Advocacy fatigue from constant justification
• Limited professional development

Coordination challenges:

• No single source of organizational truth
• Difficult to report overall accessibility status
• Regulatory responses require coordination
• Shared problems solved separately

Hybrid Models that Work in Practice

Centralized Standards, Distributed Execution

The most effective organizations often combine models:

CoE responsibilities:

• Define accessibility standards and requirements
• Create and maintain guidelines and documentation
• Develop training programs and materials
• Provide consultation for complex issues
• Audit and verify compliance
• Report organizational status to leadership
• Coordinate responses to legal/regulatory inquiries

Team responsibilities:

• Implement accessibility per standards
• Include accessibility in definition of done
• Conduct first-level testing
• Escalate complex issues to CoE
• Participate in training
• Designate accessibility champion

The Champions Model

How does an accessibility champions network support governance? Champions are team members (not dedicated accessibility roles) who receive additional training and serve as first-line accessibility resources for their teams, connecting to central expertise for complex needs.

Champions model structure:

Accessibility Leadership (executive sponsor)
          ↓
Center of Excellence (dedicated specialists)
          ↓
Champions Network (trained team representatives)
          ↓
Product Teams (all members have baseline training)

Champion responsibilities:

• First point of contact for team accessibility questions
• Conduct initial accessibility reviews
• Escalate complex issues to CoE
• Share learnings from CoE back to team
• Advocate for accessibility in planning
• Participate in champions community

CoE role in champions model:

• Train and support champions
• Run champions community (meetings, Slack)
• Escalation point for champion questions
• Conduct complex audits champions can't do
• Maintain and update standards
• Provide oversight without bottleneck

Governance Artifacts and Cadence

Essential Governance Documents

Document your governance model:

Accessibility policy: Organizational commitment, scope, standards, accountabilities.

Standards and guidelines: Technical requirements, design patterns, testing requirements.

Roles and responsibilities: RACI for accessibility tasks across functions.

Escalation procedures: What to do when accessibility issues arise or standards conflict with deadlines.

Training requirements: Who needs what training when.

Governance Cadence

Regular rhythms sustain accessibility:

Steering committee: Quarterly executive review of accessibility status, risks, and investments.

Review board: Monthly review of audit findings, patterns, and standards updates.

Champions community: Biweekly or monthly champions meeting for training, sharing, and coordination.

Team practices: Sprint-level accessibility verification, release gates, retrospective inclusion.

Annual review: Comprehensive assessment of governance effectiveness and adjustments needed.

Metrics for Governance

Track governance effectiveness:

Coverage metrics:

• Percentage of teams with accessibility training
• Percentage of products with accessibility testing
• Champion coverage across teams

Quality metrics:

• Accessibility issues found in production vs. development
• Severity distribution of issues
• Time to remediation

Process metrics:

• Champion engagement (meeting attendance, escalations)
• Training completion rates
• Audit coverage

How TestParty Supports Any Governance Structure

Shared Dashboards for CoE

TestParty provides centralized visibility:

Organizational overview: See accessibility status across all properties and teams.

Trend tracking: Monitor improvement or regression over time.

Issue patterns: Identify systemic issues requiring standards updates.

Reporting: Generate executive summaries and detailed reports.

Team-Level Views for Embedded Squads

TestParty supports distributed execution:

Product dashboards: Each team sees their properties' accessibility status.

Issue ownership: Issues assigned to responsible teams.

Progress tracking: Teams track their remediation progress.

Integration: CI/CD integration fits team workflows.

Flexible Governance Support

Whatever model you choose:

For CoE models: Central dashboard, audit scheduling, organization-wide reporting.

For embedded models: Per-team views, team-specific integrations, distributed ownership.

For hybrid models: Hierarchical reporting, champion-level access, coordinated views.

Frequently Asked Questions

How many accessibility specialists do we need for a CoE?

Rough guideline: one specialist per 50-100 developers for hands-on work, scaling with how embedded specialists or champions share the load. Consider: audit frequency needed, consultation demand, training requirements, and organizational complexity. Start smaller and grow based on actual demand.

How do we handle accessibility when teams resist?

Executive sponsorship is essential. Accessibility must be a requirement, not a request. Build accessibility into team goals and evaluation. Make it easier (better tools, training, support) before making it mandatory. Address root causes of resistance (lack of knowledge, competing priorities, skepticism about importance).

Should accessibility be part of every team or specialized?

Both. Every team needs baseline accessibility capability—inclusion in definition of done, basic testing ability, awareness of requirements. Specialized expertise (deep auditing, complex remediation, standards development) can be centralized or distributed based on your model, but every team should be able to do fundamentals.

How do we choose between CoE and embedded models?

Consider: organizational culture (command-control vs. autonomous teams), existing governance patterns (do you have other CoEs that work?), accessibility maturity (less mature often needs central guidance), scale (small orgs may not need CoE), and talent availability (can you hire embedded specialists for every team?).

When should we change our governance model?

Signs you need change: persistent bottlenecks, accessibility regression despite effort, teams feeling unsupported, inconsistent quality across products, or governance not matching organizational changes. Review governance annually and adjust based on evidence.

Conclusion: Choose the Model That Matches Your Culture and Scale

Accessibility governance isn't one-size-fits-all. The best model matches your organization:

CoE model fits when:

• Centralized governance aligns with culture
• Deep expertise is essential
• Organization-wide consistency is priority
• You can staff and scale the CoE appropriately

Embedded model fits when:

• Autonomous teams are cultural norm
• Scale makes central bottleneck untenable
• Teams can hire/develop accessibility expertise
• Coordination mechanisms exist for consistency

Hybrid models fit when:

• You want standards consistency with execution agility
• Central expertise can enable rather than bottleneck
• Champions network can bridge central and distributed
• You're pragmatic about mixing approaches

Whatever model you choose, governance must be explicit, documented, and enforced. Accessibility without accountability is accessibility without results.

Unsure how to structure accessibility ownership? Book a session and we'll prototype a governance model using your org chart and data.

Related Articles:

• Building an Accessibility Champions Network That Actually Works
• Score Your Accessibility Program: A Practical Maturity Model for 2025