Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

I think this site is not good for it because  it's mostly it can be devs producing games in jams, where the time limit means there's little time for accessibility implementation.

And in a way, that's part of the problem - that it's so time-consuming that devs often can't do it. There need to be better ways for devs to feel able to support a11y, extra tools for engines and the like. It's unfortunate that in some cases I'm seeing the engines themselves not providing key features.

What I would love to see for game jams is that after the submission deadline, there's some way for devs to add in missing a11y features. But when devs are more practiced with it, they would probably be able to do it as they went because they would know the implementation patterns. Particularly where in some cases, the a11y feature is actually the absence of a game mechanic, or is a handy feature for testing, and hence feature-flagging those mechanics straight away means you only need to provide the mechanism to set the flag. I would love to see more discussion about good practice like this.

https://itch.io/games/in-jam 352k

https://itch.io/games/exclude-jam 782k

I would not say that it is mostly devs doing jams here, what with twice the games not being in a jam.

With most games using some sort of engine, the accessibility features should be done at engine level. A single developer has neither the time nor the expertise to develop these things every time. Same as a dev would not implement a save mechanic for a renpy game. It comes with the engine. You do not want to have each developer coming up with their own clever way of saving.

Also, most devs will not have the capability to even test out their accessibility features. They cannot even test the game for different platforms. How does one test a color blind mode, if one is not colorblind?