Session recap · CSUN 2026 · WebCon 2026
What this talk covered
Most accessibility programs don't fail because people don't care—or because tools and guidelines don't exist. They fail because no one has created the organizational conditions for accessibility to succeed. This session addressed that leadership gap directly.
The session opened with an uncomfortable truth: WCAG exists. Testing tools exist. Training exists. The gap is almost never knowledge—it's leadership. Someone with authority who makes accessibility non-negotiable, and who creates the conditions where inclusion can actually happen. As the session framed it: checklists don't change cultures. Leaders do.
From there, the session covered three frameworks that give leaders practical tools to act on:
The accessibility maturity model
Organizations progress through four predictable stages: Reactive (addressing issues only after complaints), Compliant (meeting minimum standards), Proactive (integrating accessibility into processes), and Embedded (accessibility as a core value that drives innovation). The goal isn't to leap to Embedded overnight—it's to identify the current stage and lead toward the next one with intention.
ADKAR applied to accessibility change
Most stalled initiatives are stuck at Desire or Ability—not Awareness. Organizations jump straight to training before people understand why accessibility matters or have any motivation to participate. The ADKAR model helps leaders diagnose which gap they're actually facing: Awareness, Desire, Knowledge, Ability, or Reinforcement—before choosing a response strategy.
Accessibility as a non-functional requirement
Organizations already manage security, scalability, and availability as non-negotiable quality attributes. Accessibility belongs in the same category. WCAG provides a measurable, technology-neutral requirement set—roughly 50–60% validatable with automated tools—making accessibility something you can plan for, track, and integrate into agile Definition of Done criteria like any other quality standard.
The session closed with a 90-day action planning exercise: one conversation to build awareness or secure sponsorship, one process change to make accessibility a requirement, and one early win to celebrate and build momentum. Small, intentional actions compound.
The real problem this solves
Most accessibility programs don’t fail because people don’t care. They fail because the system makes accessibility optional: unclear ownership, siloed teams, late-stage QA, and incentives that reward speed over quality.
This session gives leaders a clear model for shifting accessibility from “someone’s job” to “how we deliver.”
Ownership that sticks
Where responsibility breaks—and how leaders repair it without creating bureaucracy.
Earlier becomes real
Simple interventions that move accessibility upstream into planning and design.
Shared language
The vocabulary that helps cross-functional teams make better decisions under pressure.
Quality + trust
Framing accessibility as customer experience—not just a compliance narrative.
Learning objectives
- Recognize leadership behaviors that create durable accessibility outcomes.
- Identify common cultural failure modes (silos, “late QA,” unclear ownership).
- Use simple interventions to shift responsibility earlier in the lifecycle.
- Frame accessibility as quality and customer trust—not compliance.
How it adapts to your audience
The core model stays the same, but examples and pressure points change by context: enterprise product orgs, regulated environments, or higher-education web teams.