Tips for building your own accessibility program

gamedeveloper.com:

A common refrain from accessibility advocates in game development is that the best way to support players with disabilities is to start designing features around their needs from day one. Settings for color-blind players, text-to-audio descriptions, and other tools are easier to implement if they're accounted for early rather than shoved in at the end of production.

But every developer knows every game comes with its own unique accessibility quirks. For instance, first-person shooters may need to account for PTSD triggers for those who've been around gun violence, whereas cozy farming simulators don't. Cozy farming simulators may benefit from features that reduce cognitive load for neurodivergent players, but those same cognitive load reductions may not work for a 3D platformer, and so on and so forth.

However, developers and publishers have options. Many high-profile studios are already rolling out extensive accessibility features, and publishers like Whitethorn Games are establishing accessibility pipelines to support the smaller teams working across many genres. For insight on how those pipelines are structured, we checked in with chief accessibility officer Britt Dye for a look at her day-to-day workflow and a discussion about how accessibility can be approached at studios of all shapes and sizes.

Dye has a rather fun background as a chief accessibility officer. She began her professional career in the world of library science and eventually transitioned into the world of user research. She began to think about how product usability and accessibility go hand-in-hand, finding frequent intersectionality between the two worlds.

"The skill set is pretty well aligned," she said when pressed about how library science can lead