One Accommodation at a Time

Apple is supposed to be the gold standard for accessibility. They get praised for it. VoiceOver is genuinely good. Touch Accommodations exist for people who need help interacting with the screen. Both features are built by Apple, both are designed for disabled users, and both are mutually exclusive.

I found this out by accident. I was setting up Touch Accommodations on my iPhone, trying to make the screen easier to use. I got everything configured the way I wanted. Then I turned off VoiceOver for a minute to show my mom something. When I turned it back on, I got a message: Touch Accommodations are disabled when VoiceOver is active.

I need both. I’m blind. I use VoiceOver because I can’t see the screen. I also have motor and sensory differences that make touch interaction harder, and Touch Accommodations help with that. Two accommodations that each solve a real problem, and together they solve a problem neither one alone can address. Apple’s response is: pick one.

That’s not a bug. Someone at Apple decided that Touch Accommodations and VoiceOver are for different people. Not for the same person. Because in the framework that drives most accessibility design, you’re either blind or you have motor impairments. You’re not both.

I’m both. A lot of disabled people are both.

The Dictation Problem #

Here’s another example, from a different system, with the same flaw.

I have rheumatoid arthritis. When it flares, my hands hurt. Sometimes I can’t type. In college, the pain got bad enough that I contacted disability services. I was writing my papers using LaTeX, a markup system that let me write efficiently with a keyboard. Their suggestion: stop using LaTeX, switch to Word, and use Word’s built-in dictation.

They knew speech could be hard for me. I had told them. But dictation is the standard accommodation for hand pain. It’s in the playbook. Hand pain equals dictation. They checked the box and sent me on my way.

Here’s why that doesn’t work for me.

I’m blind, so I use a screen reader. Dictation doesn’t work well with screen readers on Windows. The two tools fight each other. I’m also autistic, and my speech can be disfluent. Dictation struggles to understand me when I pause to find a word, when I lose my train of thought, or when my speech doesn’t come out in clean, complete sentences. I have cognitive fatigue from chronic illness, and the frustration of dictation timing out or inserting wrong words isn’t just annoying. It drains me in a way that costs me the rest of my day.

So the accommodation for my hand pain creates new problems for my blindness, my speech, and my cognitive fatigue. Four disabilities, one accommodation, and it helps one while making the other three worse.

That’s not accessibility. That’s a trade-off disguised as a solution.

I tried Word’s dictation. I’d pause to find a word and it would time out. It would insert things I didn’t want. I’d spend more energy fixing what dictation got wrong than I would have spent just typing through the pain. The tool that was supposed to help me ended up costing more than the problem it was solving.

And nobody in that disability services office sat down and thought: this student has hand pain and uses a screen reader and has speech disfluency, so dictation is going to be a disaster for her. Because thinking that way requires understanding how disabilities compound, and that’s not in the training. It’s not in the policy. It’s not in the playbook.

The Pattern #

Both of these come from the same place.

Apple built two accessibility features and made them mutually exclusive because they assumed nobody would need both. Disability services prescribed dictation because they have a list of accommodations and hand pain maps to dictation. One condition, one accommodation, one box checked.

This is the single-disability framework. It’s everywhere. In technology, in education, in healthcare, in every system designed to serve disabled people. The assumption is that disabled people have one condition, one set of needs, one accommodation that will fix it. You check the box and you’re done.

When you have one disability, the framework mostly works. You’re blind, you get a screen reader. You have a motor impairment, you get touch accommodations. You have hand pain, you get dictation. One problem, one solution.

When you have multiple disabilities, the framework breaks. Because your accommodations interact. Your screen reader doesn’t work with your dictation software. Your touch accommodations turn off when your screen reader turns on. Your dictation can’t understand your disfluent speech. Each accommodation helps one condition while making another one worse. And nobody designed for that intersection, because nobody imagined someone would be standing in it.

I’m blind. I’m autistic. I have rheumatoid arthritis, fibromyalgia, IIH, gastroparesis, esophageal dysmotility, IBS, topographical agnosia, chronic pain, cognitive fatigue, and a body that’s been fighting itself for 34 years. I don’t have one accessibility need. I have a dozen, and they interact with each other in ways that no single-accommodation framework can handle.

Apple could fix the Touch Accommodations and VoiceOver conflict. They could figure out how to let both run at the same time, or at least let the user choose which features within each one to combine. But they haven’t, because in their framework, the blind person and the person with motor impairments are two different users. The possibility that they might be the same person doesn’t enter the design process.

Disability services could have offered me alternatives. An alternative keyboard. A voice recognition tool that works better with screen readers. A conversation about what my actual workflow looks like and what would fit it. But they didn’t, because in their framework, hand pain has one answer, and the answer is dictation. Whether it works for me or not.

What It Costs #

The cost of this framework isn’t just frustration. It’s real.

When Apple turns off my Touch Accommodations, I lose a tool that helps me interact with my phone. I’m desktop-first. My computer is my primary device. My phone is something I have to have, not something I want to use. Touch is hard for me. Navigating a spatial screen is hard with topographical agnosia. Holding the phone can be fatiguing. My motor issues, my fatigue, my other disabilities all stack against it. If I could, I’d switch entirely to a computer and not have a phone at all. But you have to have a phone these days. Some apps don’t even have desktop equivalents. So I’m stuck with a device that’s already difficult for me, and when I finally get it configured to work better, the configuration vanishes the moment I turn on the one accessibility feature I can’t live without. Losing an accommodation I need because I activated another accommodation I need is not a design choice. It’s a door that closes behind you when you walk through a different one.

When disability services prescribed dictation, they didn’t just give me a bad tool. They told me to abandon the tool that was working, LaTeX, and replace it with one that wouldn’t. That’s not just unhelpful. It’s actively harmful. I went from a workflow that let me write despite my hand pain to one that made writing harder across the board, for all the reasons dictation doesn’t work for me. The accommodation was worse than the problem.

This is what the single-disability framework costs. It doesn’t just fail to help. It creates new barriers while pretending to solve the ones you already had. And the person it happens to is left to figure out why the system that was supposed to help them made things worse.

I shouldn’t have to choose between seeing my screen and touching my screen. I shouldn’t have to choose between my hands and my voice. I shouldn’t have to abandon a workflow that works because someone with a checklist decided my problem was simpler than it is.

Disabled people with multiple conditions aren’t rare. We’re not edge cases. We’re not a niche use case that accessibility teams can deprioritize. We’re a significant part of the disabled population, and we’re the ones who fall through the cracks in every system built for one disability at a time.

The framework needs to change. Not just at Apple, not just in disability services. Everywhere. The assumption that disabled people have one need, one accommodation, one box to check is wrong. It was always wrong. And the people it fails the hardest are the ones who need accessibility the most.