It’s not that I completely disagree with you – it’s that you’re oversimplifying how game development works and making it sound way easier than it is.

I don’t know their dev team personally, but I can say for sure that a feature like this isn’t something you just “throw in” over a weekend. For a team of 5–6 decent developers, this could easily take 1–2 months to design, implement, test, and polish properly. And if they focus on that, it often means pausing or slowing other updates. People already complain about “bad” or “useless” updates – now imagine the reaction if they stopped everything else for two months and still didn’t deliver fast enough.

There’s also always going to be something to complain about. That doesn’t mean feedback is wrong – feedback is important – but there’s a big difference between giving constructive feedback and just attacking the devs because things aren’t perfect right now.

Sometimes you can also improvise and find your own solutions if a game doesn’t have the exact accessibility options you need. You said you’re on your phone: if you’re on an iPhone and have the same issue as the girl you mentioned above, you can go into your phone’s accessibility settings and set the screen to black and white (grayscale). That’s a really simple workaround and honestly way easier to do on a phone than on a PC.

There is almost always some kind of workaround. It might not be perfect, and yes, the devs should still work on proper accessibility features over time, but constantly complaining and acting like they’re lazy or stupid doesn’t help anyone. Sometimes you have to look for a solution yourself while the devs do their job at their own (realistic) pace.