Accessibility Ultimatums
When care is crowdsourced -- and access demands labor.
What It Isβ
An accessibility ultimatum is a disabling force. It occurs when builders create infrastructure that offloads the responsibility for facilitating accessibility onto navigators. The navigator faces a choice: do the work of removing the accessibility barriers, or endure inaccessibility. Both options cost the navigator. Neither option is the navigator's fault.
A video streaming platform builds a captioning tool and volunteers produce the captions. A university provides an accommodation process and students navigate, document, and defend their own access. An overlay vendor deploys a widget and disabled users configure it on every site. In each case, the builder built something, but what they built is not access. It is infrastructure that makes the navigator responsible for producing access.
When a builder is absent, neglect is obvious. When a builder is present and facilitates navigator-side labor, neglect looks like a feature. The platform works for most people. For disabled people, it works only if they do additional work. The facilitation makes this feel generous. The structure makes it compulsory.
Why It Happensβ
Accessibility ultimatums happen when builders treat disabled people's labor as a resource rather than a cost. The builder needs captions, so the builder builds a captioning tool and lets volunteers do the work. The builder needs accessibility testing, so the builder builds a feedback form and lets users report failures. The builder needs route data, so the builder builds a mapping app and lets wheelchair users survey their own neighborhoods.
In each case, the builder builds infrastructure. The navigator does the work. The builder saves the cost. In economic terms, the builder externalizes the cost of accessibility to the people who need it most.1 The navigator pays it in time, energy, and capacity that could have been spent elsewhere.
Asymmetry enables accessibility ultimatums. Everyone uses the same platform, but only disabled people face the additional labor. The ultimatum falls on the people already bearing the cost of inaccessibility.
Framing disguises accessibility ultimatums. The labor is presented as participation, community, or empowerment. YouTube called volunteer captioning "community contributions." Overlay vendors call widget configuration "personalization." Universities call accommodation paperwork "self-advocacy." The framing makes the labor feel voluntary. The underlying structure makes it compulsory: do the work, or go without.
Self-accommodation fuels accessibility ultimatums. The American Bar Association describes self-accommodation as disabled people doing "all the ordering, paying, transporting, and moving" that the law says the employer should cover.2 The ABA frames this as "a rational response to inaccessible systems." Accessibility ultimatums depend on that rationality. The builder builds infrastructure that works only if navigators self-accommodate through it. The navigator's willingness to do the work becomes the resource the builder's system runs on.
Normalization protects accessibility ultimatums. When the labor has always been the navigator's, no one questions it. The self-checkout doesn't announce that the cashier was fired. The community caption tool doesn't announce that the platform chose not to caption its own videos. The overlay doesn't announce that the builder chose not to fix the markup. The arrangement is presented as the way things are. The navigator who objects is the one who seems unreasonable.
Where It Happens (ENABLE Stages)β
| ENABLE Stage | How Accessibility Ultimatums Show Up |
|---|---|
| Set Requirements that Include Accessibility | The builder defines accessibility as user-configurable rather than built-in. Navigators must configure their own access on every use. |
| Create Accessible Content | Content is published without captions or transcripts, but with tools for volunteers to contribute them. |
| Design Accessible Experiences | Instead of fixing the underlying design, the builder adds a customization feature. Navigators do the actual design work of making it usable for themselves. |
| Develop Accessible Implementations | Instead of remediating the underlying code, the builder develops an SDK or API for plugins and extensions, and navigators produce the code fixes. |
| Test for Accessibility | The builder ships feedback forms and bug reporting tools instead of testing. Navigators perform the QA. |
| Triage and Prioritize Accessibility Issues | The builder creates prioritization processes that require navigator advocacy. Issues are triaged only when navigators push for them. |
| Iterate to Address Shortcomings | The builder builds crowdsourcing tools (user ratings, route maps, flag-as-inaccessible buttons) instead of surveying and remediating. Navigators supply the data that drives iteration. |
| Provide Support Channels | The builder creates a separate accessibility desk, hotline, or interpreter line while leaving the ordinary service path inaccessible. Navigators must self-identify, disclose, or call a special queue to get ordinary service. |
| Create Stopgaps | The builder hosts community forums or knowledge bases where navigators share their own workarounds. The builder provides the venue. Navigators produce the stopgaps. |
How It Disablesβ
Accessibility ultimatums disable by making disabled people run extra cycles, consuming capacity that only disabled people are asked to spend. A hearing viewer simply watches a video. A hard of hearing viewer captions it, too. A sighted user simply browses a website. A low vision user files a bug report about missing labels, too. A non-disabled student simply enrolls in a course. A disabled student spends hours arranging accommodations before the course begins, too. Everyone uses the same platform. Only some people must labor to make it work.
- It imposes asymmetric labor: the disabled navigator did not create the barrier, but the disabled navigator is the one who must choose between removing it or going without.
- It consumes opportunity: every hour spent producing access is an hour not spent using it.3
- It paralyzes: The decision fatigue experienced when a navigator is constantly presented with the ultimatum (undergo labor or endure inaccessibility) can be paralyzing.
- It disrupts existing tools: as the Overlay Fact Sheet documents, "any person with a disability has their favorite set of tools and browser settings already tuned and learned. Forcing a user with disabilities to scrap their tools to then study, learn and customize this new set of toolbar options for each website they visit is a serious barrier."4
- It resists compensation: unlike shadow work (Illich, 1981),5 invisible labor (Daniels, 1987),6 and digital labor (Fuchs, 2014),7 accessibility ultimatums do not resolve with payment. Pay a deaf viewer for captioning and they still spent time captioning instead of watching. The labor is the harm, not the absence of compensation.
Accessibility ultimatums disable by making inclusion a task that only disabled people are assigned.
Why It Mattersβ
Accessibility ultimatums get into the body, reshape behavior, and erode the systems meant to provide inclusion.
Accessibility ultimatums are common and rarely named. They hide inside tools that look helpful, processes that look fair, and language that sounds empowering. Accessibility ultimatums erode capacity, produce chronic stress, inflict structural violence, disguise neglect, compound across systems, undermine rights frameworks, predate the term, reward builders, sustain themselves, and teach disabled people that their inclusion is conditional.
Accessibility ultimatums erode capacity. In higher education, researchers documented that disabled students' self-advocacy labor ranged from "one hour per semester" to "four hours a day."8 Students performed "emotion work" to maintain composure "even when justifiably emotional in the face of ableism." Faced with the ultimatum, many chose to accept partial accommodations rather than advocate for full needs, take grade penalties instead of requesting extensions, or drop courses entirely. One student chose to drive an hour each way to pick up medication off-campus rather than attend three self-advocacy meetings, prioritizing energy conservation over time efficiency. The student made a rational calculation: the labor of navigating the system cost more than the labor of working around it.8
Accessibility ultimatums produce chronic stress. Each ultimatum is a stressor. Across platforms, days, and years, the body accumulates the toll. Bruce McEwen's concept of allostatic load describes the "wear and tear on the body" from repeated adaptation to chronic stress.9 Ilan Meyer's minority stress model, recently adapted to disability, identifies structural ableism as a distal stressor that produces proximal effects: vigilance, anticipation, and internalized devaluation.10 The navigator who scans every new website for accessibility barriers before attempting to use it is not being cautious. They are managing a stress response that the builder's infrastructure imposed.
Accessibility ultimatums inflict structural violence. In Johan Galtung's sense, the harm is "built into the structure" so that "there may not be any person who directly harms another person."11 The builder could have captioned the videos, fixed the markup, tested with screen readers, or surveyed the routes. The builder chose to build infrastructure that makes the navigator do it instead. Disabled bodies are placed in harm's way, not all bodies.
Accessibility ultimatums disguise neglect. A platform with no captions is obviously neglectful. A platform with a crowdsourced captioning tool looks like it cares. The tool's existence obscures the fact that the barrier not only persists, but the labor to remove it has shifted from builder-side to navigator-side.
Accessibility ultimatums compound. Each ultimatum a navigator faces is one of many. The same person who configures an overlay on one site files a bug report on another, arranges accommodations at work, and maps an accessible route home. The labor accumulates across every system the navigator touches.
Accessibility ultimatums undermine rights frameworks. The ADA requires builders to provide access. An accessibility ultimatum satisfies the letter of that requirement by building a tool. But the tool shifts the labor to the navigator. The right exists on paper. The access exists only if the navigator activates it. Legal protections that depend on navigator labor to function become rights in name only.
Accessibility ultimatums predate the term. The pattern is as old as institutions building "for" disabled people. The charity telethon built a fundraising platform. Disabled people performed on it. The sheltered workshop built a workplace. Disabled workers produced below minimum wage. The accommodation office built a process. Disabled students navigated it. The ENABLE Model names a pattern that disabled people have always recognized but that builders have rarely been asked to see.
Accessibility ultimatums reward builders. The builder gets credit for the tool. The navigator's labor produces the access. The builder's investment report lists the feature. The navigator's hours do not appear in it.
Accessibility ultimatums sustain themselves. The builder saves money by externalizing accessibility labor. The language of empowerment and participation protects that savings from scrutiny. The economic incentive produces the ultimatum. The political framing legitimizes it. Neither can persist without the other.
Accessibility ultimatums teach disabled people that their inclusion is conditional. The message, repeated across every platform and institution, is clear: you are welcome here if you do the work. The ultimatum does not say "you are excluded." It says "you are included, provided you labor for it." Over time, some stop laboring. Others stop showing up. What looks like disengagement is often self-preservation.
Real-World Examplesβ
When the System Fails: Why Disabled People Self-Accommodate
-- Katherine A. Macfarlane, American Bar Association
- The ABA describes self-accommodation as disabled people absorbing the labor and cost that the law assigns to employers and institutions. Self-accommodation is "a rational response to inaccessible systems, not the result of an information deficit." The ultimatum is structural: when formal processes are too slow, too adversarial, or too exhausting, disabled people do the work themselves rather than going without.2
Politicizing Self-Advocacy: Disabled Students Navigating Ableist Expectations in Postsecondary Education
-- Emunah Woolf and Alise de Bie, Disability Studies Quarterly
- Researchers found that disabled students' self-advocacy labor consumed up to four hours a day. Students performed emotional labor to manage nondisabled people's reactions, with one reporting that the emotional toll created "a lot of extra pain afterwards" requiring days of recovery. Many students chose to accept partial accommodations, take grade penalties, or drop courses rather than continue advocating. The ultimatum: spend your limited capacity fighting the system, or accept less than you need.8
Overlay Fact Sheet
-- Signed by 1000+ accessibility professionals
- Over 1000 accessibility professionals signed a statement opposing overlay widgets. The fact sheet documents that overlays force disabled users to "scrap their tools" and "study, learn and customize this new set of toolbar options for each website they visit." Overlays present disabled users with an ultimatum: configure the widget on every site, disable it, or leave. According to UsableNet's 2024 data, 25% of all digital accessibility lawsuits targeted websites using overlays, cited as barriers, not solutions.4
- YouTube's community captions feature allowed volunteers to caption videos, shifting builder-side content labor to navigators. The feature was abused by trolls and removed in 2020. The Google manifestation page documents the ENABLE Model question: whether the builder-side tools that remained were adequate to make that navigator-side labor unnecessary.
- Crowdsourced accessibility maps (such as AccessNow and Wheelmap) let wheelchair users rate and flag accessible locations. The data is valuable. The labor of surveying every restaurant, hotel, and transit station falls on the people who need the data most rather than the businesses that own the spaces.
- reCAPTCHA, as documented in the Google manifestation, presents an ultimatum to blind and deaf users: solve a challenge designed for sighted and hearing people, find a workaround, or be blocked from the site entirely.
What Care Sounds Likeβ
"We caption our own videos before publishing. We don't ask viewers to do it." "We caption our content before publishing, not after complaints." "We test with disabled users before launch, not after complaints." "We fix the markup. We don't deploy a widget and call it accessible." "Accommodation is an institutional responsibility, not a student's second job."
What Neglect Sounds Likeβ
"Users can add their own captions." "The overlay gives users the tools to customize their experience." "Students are expected to self-advocate for their accommodations." "We have a feedback form for accessibility issues." "The community can flag inaccessible locations."
The ultimatum is labor or exclusion. ENABLE names this force so that builders cannot present the navigator's additional labor as a feature.
We gotta make a decision. Leave tonight or live and die this way -- Tracy Chapman
Footnotesβ
-
American Bar Association: When the System Fails: Why Disabled People Self-Accommodate β© β©2
-
Disability Studies Quarterly: Politicizing Self-Advocacy: Disabled Students Navigating Ableist Expectations β© β©2 β©3
-
Bruce McEwen and Eliot Stellar: Stress and the Individual: Mechanisms Leading to Disease (1993) β©
-
Ilan Meyer: Minority Stress and Mental Health in Gay Men (1995) β©
-
Johan Galtung: Violence, Peace, and Peace Research (1969) β©