4 ms·
Or, not every UI library is intended for use cases where a13y even makes sense. Like a debug UI in a game engine, or in an embedded device that doesn't even ha
by monocasa 4mo ago
Or, not every UI library is intended for use cases where a13y even makes sense.
Like a debug UI in a game engine, or in an embedded device that doesn't even have input for a13y.
- fwip 4mo agoBeing accessible to the intended users always matters. If you think it doesn't, that probably means it's currently accessible to those users (or that those who are it is inaccessible to have filtered themselves out, and are no longer users). For example - in your debug UI, colorblind-friendly colors don't matter, until you hire your twelfth member of the team, who struggles to tell red and green apart.
- monocasa 4mo agoThis library's default is greyscale anyway, so it's by default colorblind friendly.
- Intralexical 4mo agoAdditionally the developer of this library is active in the indie game scene, so "twelfth member of the team" is hardly a relevant issue. I find it so unfortunate how many of the criticisms raised here are mooted by simply glancing at the README. There's an interesting conversation that could be had about the needs and limitations for debug UIs, and how to balance that with minimal code. (E.G. Would feeding this library's text-and-rectangles output into an accessible renderer be enough?) But blanket rejections and reflexive judgement aren't helpful.