7 ms·
> "We have working accessebility for all applications throughfully designed with native OS controls." The comment I'm responding to says that progress bars in
by csmpltn 5y ago
> "We have working accessebility for all applications throughfully designed with native OS controls."
The comment I'm responding to says that progress bars in the terminals, and that TUIs in general are an accessibility nightmare.
Are you disagreeing? Are you claiming that it's a solved problem? Would you mind elaborating on what you think can be done to solve this?
- nightpool 5y agoYou're misinterpreting the GP's post, TUIs are not "thoughtfully designed with native OS controls".
- csmpltn 5y agoNo, that's exactly my point. The bulk majority of applications people use today are not "thoughtfully designed with native OS controls". Sprinkling some ARIA labels around is better than nothing, but the experience itself is extremely limited and is not on-par with what those people deserve. I'm talking about Javascript/CSS-heavy websites in a web-browser, computer games, or software such as Blender/SketchUp/Google Earth to name a few. ARIA labels aren't good enough here - we would need to develop an entirely different interface to accomodate for each individual accessibility scenario. You can imagine a blind person and a deaf person using entirely different versions of Blender, each built with a different interface accomodating a specific disability.