You have to remember that billions of dollars aren't disposable, and a developer still has to worry about investment vs return. This probably doesn't apply as much for tts, but I know for a full interface redesign it costs a lot up front and if they are going to throw in all this money and get a measly return value then what's the point? I hate to sound like that but it's true. Now for tts that is entirely a different story and is technically very easily implementable, however, outmoded publishers may not approve, and can come up with whatever bullshit excuse they want. When it comes to big game companies and their relationships with publishers, they'd rather keep them happy to keep funds growing. It's why, other than EA and NRS, you see more accessibility work being done from Indie developers. It also could simply be the engine they're using not allowing it. I unfortunately believe that is what happened to Way of the Passive Fist and why it can't get more accessibility features, because the engine won't allow it. Which sucks ass, but a developer is not going to practically rewrite the game in a different engine just to satisfy accessibility needs. I'm sorry, that's just not a realistic expectation. As for the engine limitations, I actually have seen that be an active concern for a developer (off topic from games) but I was talking with Goldwave on Twitter about how accessibility were to look on the up and coming Goldwave For mobile (ios and android.) To make a long story short, they basically said a lot of things which led to don't gets your hopes up too high for the initial release. Their cross-platform engine has absolutely no way to communicate with either text to speech api, and has no accessibility support implemented. The only thing close to that is that they just released an update allowing native controls, and I told Goldwave that as long as those native controls are properly labeled the thing should be accessible to a point.
So there you have it. Granted, there are some game developers who will be purposefully ignorant and choose not to make accessibility a priority. But I will say those voices are gradually holding less weight and more developers are at least considering accessibility.
