How different stakeholders use the ENABLE Model
A product manager reviewing a broken signup flow, a policy staffer drafting procurement language, a professor updating a medical-school curriculum, and a disabled user composing a bug report share the same underlying question. Someone earlier in the chain shifted the cost of access onto someone later. The ENABLE Model supplies a shared vocabulary for naming where the shift happened and which decision would have prevented it.
Readers approach any broken experience by answering four questions:
- Where could access have arrived earlier, through builder-side interventions?
- Who is carrying the burden now, through navigator-side compensations?
- What structural conditions created or sustained the gap, as forces that disable or forces that enable?
- What have specific actors actually done in response, documented across the manifestations corpus?
Each stakeholder group answers those questions from a different position.
Builders, designers, and developers
Builder-side interventions cover ten stages where product teams can prevent the barrier before a disabled user encounters it.
Product owners and engineering leads set requirements that name accessibility as a shipping condition rather than a backlog ticket. Microsoft's supplier clauses require WCAG AA conformance; the team that wrote that clause decided accessibility was non-negotiable before any vendor wrote a line of code. Finance and staffing leaders provision resources so that the requirement becomes a hired team, a line item, and protected hours. Enable Ventures ties investment tranches to inclusion metrics so that the resource decision precedes the product.
Content creators, designers, and developers write accessible content, design accessible experiences, and develop accessible implementations. Deque's axe-core and the WebAIM WAVE evaluator catch a subset of issues before launch. Screen-reader testing with NVDA, VoiceOver, and JAWS catches what the automated tools miss.
QA engineers test for accessibility with disabled participants. Fable sells disabled-user testing as a managed service because Shopify, REI, and other enterprise customers had not built the panels themselves. Accessibility teams triage findings against release criteria and iterate on the reports that come back from users and assistive technology vendors. Customer-facing teams run support channels that stay open to disabled users rather than routing them to a chatbot that cannot process their issue. Engineering leads create stopgaps, temporary accommodations that reduce harm while a full fix is built, and commit to a deprecation timeline so that the stopgap does not become the permanent architecture.
Leaders, policymakers, and decision-makers
Executives and policymakers set the conditions that determine whether any of the builder-side stages actually run. The federal Section 508 program and the U.S. Access Board produced the procurement standards that Microsoft, Adobe, and Apple now cite in their Voluntary Product Accessibility Templates. The European Commission wrote the European Accessibility Act in 2019 and required member states to begin enforcement in June 2025. California Assembly Bill 434 in 2017 set state-agency web accessibility deadlines that most California departments missed on the original timeline but have progressed against since. Each of these documents moved requirement-setting upstream of product teams.
Leaders who refuse to budget for long-term maintenance invite abandonment. Secretary Marco Rubio reversed the State Department's 2023 adoption of the Calibri typeface in December 2025, calling the accessibility upgrade "wasteful." American, Delta, JetBlue, Southwest, and United Airlines sued the Department of Transportation in February 2025 to block fines for wheelchair damage after the airlines mishandled 11,527 wheelchairs and scooters in 2023. Leadership decisions move care in both directions, and the ENABLE Model gives staff a vocabulary to name the direction and the cost.
Educators and content creators
Curriculum authors decide what the next generation of builders learns. Gallaudet University, under the leadership of Roberta Cordano since 2016, teaches Deaf and hard-of-hearing students inside a bilingual ASL-English environment that most postsecondary institutions do not provide, and Gallaudet's Technology Access Program continues the research tradition Harry Lang and others established. Beacon College awards the first U.S. four-year degrees designed for students with learning disabilities and ADHD. Medical educators who teach disability as structural rather than clinical draw on the Docs with Disabilities Initiative, which Lisa Meeks co-founded to collect first-person accounts from disabled physicians and medical students.
Journalism and trade press shape what builders read. Mia Mingus's writing on access intimacy, Leah Lakshmi Piepzna-Samarasinha's Care Work, Alice Wong's Disability Visibility, and Liz Jackson's writing on disability dongles reach designers and product managers who never attended a disability-studies course. Educators who cite primary sources instead of summarizing them route their students to the archive and to the practitioners who built it.
Activists, advocates, and researchers
Advocacy organizations document the navigator-side labor that product teams do not see. DREDF files amicus briefs and shapes Supreme Court litigation. Lainey Feingold's structured-negotiation practice has produced enforceable accessibility commitments from Bank of America, CVS, Major League Baseball, and Walmart since 1995. Disability Rights Education and Defense Fund alumni Judy Heumann, Kitty Cone, and Brad Lomax organized the 504 Sit-In at the San Francisco HEW offices in 1977 alongside the Black Panther Party, occupying the building for 25 days until Secretary Joseph Califano signed the Section 504 regulations. On March 12, 1990, sixty activists climbed the Capitol steps by hand in the Capitol Crawl. Congress passed the ADA four months later.
Researchers quantify the cost of the barriers the advocates name. WebAIM's annual Million report tests the top one million homepages and consistently finds WCAG failures on more than 95 percent of them. The Bureau of Labor Statistics tracks the disability employment gap. The World Bank estimated in its 2019 Disability Inclusion and Accountability Framework that limited economic participation by disabled people costs the global economy between $1.37 and $1.94 trillion annually. Researchers who cite forces that disable by name, including precarity, accessibility ultimatums, and useless-eater rhetoric, route the policy conversation to the structural drivers rather than to isolated product defects.
Users and teammates
A disabled user who recognizes a workaround as workaround can name it, document it, and submit it as a bug report that a product team can act on. A non-disabled teammate who watches a colleague ask for help every time the expense-reporting system rejects a voice-input entry can open the ticket the colleague cannot. A manager who notices that a direct report is switching to an alternative workflow every week because the sanctioned tool is inaccessible can raise the issue as a staffing and productivity cost, not only as a compliance risk.
The endure inaccessibility category names the labor that never surfaces as a ticket, a complaint, or a switch. Users endure because prior complaints produced no fix, because the benefit-cliff math punishes the time a complaint takes, or because the emotional cost of yet another support call exceeds the cost of the barrier. Teammates who understand endurance as a compensation rather than a non-response can route the burden back upstream.
What the shared vocabulary enables
A product manager, a policy staffer, a professor, and a disabled user can now describe the same incident in the same terms. The product team's decision not to test with disabled participants produced the barrier. The barrier produced the workaround. The workaround produced the employee's wasted hours and the bug report the team never answered. The unanswered report produced the switch to an alternative and the eventual loss of the customer. The loss of the customer documents that the testing decision had a price.
The ENABLE Model makes the chain legible. Readers who want to change a specific outcome can trace the chain back to the decision that produced it and propose the intervention that would unmake it.