Errata

I realize this book is early in development, so maybe you have plans to include what I'm about to suggest.

You only talk about binaural hearing in this section. I can't hear on my left side, and encounter systems that require both ears to properly experience. Some of them, like games without video, are entirely necessary for the intended experience. Others, like music or audio programs, often use stereo sound in ways that I can't hear and there's *resistance* to implementing monoaural sound options.

Spotify, for example, won't do this because they don't think musicians "would like their hard crafted stereo mix placed in mono."

See here, search for "David": https://community.spotify.com/t5/Live-Ideas/Need-to-play-in-mono/idi-p/17377

Meanwhile, I still can't hear the mixes. That issue is from 2012.

And, sure, maybe this should be solved as a hardware issue in the computer or phone itself. Windows AND Android ship without monoaural options in their accessibility settings. The two biggest platforms in desktop and phone ignore this. And most apps don't then solve it as a software issue. Because.

I understand the initial focus on all senses working properly, but it feels incomplete to introduce them all without even a mention of the possibility of them not working. And not just for hearing-impaired people like myself, but for the blind, people who are touch-insensitive, and other groups. Accessibility awareness is important, so instances like David prioritizing hypothetical musician reaction over the user experience of the app will happen less frequently. A resource focusing on experience through senses like this book should give accessibility concerns a lot of visibility.

Note from the Author or Editor:
This was handled during rewrites. We got these comments in this category during the read through. It was great that so many cared about this topic and wanted it.