They Actually Shipped It

I wrote a review of NukeFire in August.

It was an accessibility review. I’m a screen reader user, and I went through the client and wrote down what worked and what didn’t.

Three things stood out as missing. A proper soundpack. Accessibility hotkeys. A way to review message history that a screen reader could actually navigate.

I wrote them down and published the review. Then I moved on.

This week the developer wrote back.

They added all three. The soundpack, the hotkeys, the message history. And in their public update, they linked to my review and said thank you by name.

That doesn’t happen often.

Most of the time, accessibility feedback goes into a list. It gets acknowledged, maybe, and then it sits there. The person who wrote it never hears back. The thing they flagged never changes.

This time it changed.

I’m not a compliance auditor. I don’t run WCAG checklists. I’m a player who uses a screen reader, and I wrote down what got in my way. That’s the whole method.

And it worked, because the developer was actually listening. They said every accessibility feature they’ve built came from a player’s idea or problem. I was one of those players.

There’s a version of accessibility work that’s about checking boxes. And there’s a version that’s about sitting down with the people who use the thing and asking what’s broken.

The second one is slower and messier. It doesn’t produce a certificate.

But it’s the one that actually changes the product.

You can read the original review here: NukeFire: A Post-Apocalyptic MUD That Built Accessibility Into the Wasteland