Accessibility and Apple: dizziness by a thousand cuts.

In which I try to explain the problems with Liquid Glass and the current Apple betas when it comes to vestibular conditions, outline how Apple responds to this kind of thing, and react to the three types of feedback I get when writing this kind of post.

https://reverttosaved.com/2025/07/13/accessibility-and-apple-dizziness-by-a-thousand-cuts/

Accessibility and Apple: dizziness by a thousand cuts | Revert to Saved: A blog about design, gaming and technology

Candid commentary on technology, retro games, Macs and other things, written by Craig Grannell.

@craiggrannell really great read, thanks for sharing! I'm doing a lot of accessibility work on @personalbest atm and this makes me very motivated to make sure I cover all this stuff too
@craiggrannell I liked this article. You seem to be one of the very few raising the issue of vestibular triggers. Thankfully, I’m not affected by motion-related effects, but I have a friend who once explained to me in detail why he can’t play games that have a first-person perspective. He has no problems with other games with different perspectives (isometric, third-person, top-down, etc.). And you’re right, Apple is too passive about this, and it seems one has to remind them every damn time.

@morrick Thanks re the article. And, yeah, it’s a frustratingly ignored area of accessibility. Ironically, I build the original Ménière's Society website back in the day, and drew their logo, and so learned a bunch about this stuff before it ended up affecting me.

Games are interesting. I *can* play first-person, *if* I am in control and the camera is stable. Mario Kart = fine. FPS where the camera has footstep bobs = nope. Playing Mario Odyssey as the hat: hell no.

@morrick Apple is passive but also inconsistent. Sometimes, it pushes back. Some responses I got from the macOS team a while back were just odd. tvOS doesn’t appear to care at all about this. But the iOS lot have mostly been good, and IPadOS to a similar degree.

I just wish this was all baked in. It should be foundational. And not just for Apple, but also for devs. Turn on Reduce Motion. Are the aggressive transitions calmed? if not, maybe do some extra work.

@morrick On games, I’m reminded of something that sums up how problematic this stuff can be, and why folks need to test. I once had a single-screen puzzle game I couldn’t play. Why? Because the instant you completed a level, there would be a full-screen wipe. So while the game itself was absolutely fine, the transition make me sick. (Alas, this was one dev that _didn’t_ respond kindly to feedback. Many do. I like those ones. :D )
@craiggrannell Agreed. I also think all the accessibility settings should be maintained from version to version, and also preferences should be made to stick even after a major release upgrade. So that users with vestibular concerns can enter the new version without having to run to Accessibility settings all the time. Imagine if it was something that became part of your Apple ID and could be synced across devices.

@morrick So on that side of things, I find settings do tend to stick during upgrades, but of course not across devices. However, Apple did at least (IIRC) roll in some motion reduction to its setup screens, which at one point were vestibular triggers(!!!), and Reduce Motion is now part of that on Mac at least.

More broadly, while I’m glad Accessibility has a section in Settings, those settings should be elsewhere in context too. A handful are, but more should be.

@craiggrannell Thanks for covering this stuff in detail. You would think "a good number of users find your UI nauseating" would land better as feedback.

@cstrauber It lands better when enough people shout about it. And I’m grateful Charles Arthur commissioned that Guardian piece from my pitch years ago, because that resulted in wider awareness, including at Apple.

But it is a pity that all these years later, it’s still so often a fight to even wrestle operating systems and apps to a point where they’re just about usable in this space. But, hey, I’m not going to stop shouting, even if the replies I get sometimes suggest I should.

@craiggrannell Is there a good place for non-developers to yell about this stuff? I don't usually run the betas but I am pretty good at yelling articulately.

@cstrauber If you’re running betas and discover accessibility shortcomings, file feedback. Outside of the beta, accessibility at apple dot com is the address I’ve been using.

In all cases, I’ve found requests work best with very straightforward structure:

- OS
- What happens
- Why this is a problem
- Ideal behaviour

(Or expected behaviour with the last one, if you find a big, such as the zooming and flouts on iPadOS 26 when you tap back to the ‘desktop’.)