Recent searches
Search options
If you enjoy reading accessibility battles between blind users and absolutely clueless software developers, oh boy do I have a thread for you.
This guy is trying to add accessibility to an open source slicing tool for 3d printers, he's even willing to do a lot of the work himself if he gets assurance that his PRs are going to be accepted, but the developers are just not seeing it.
I think my favorite quote in the thread is the following, from one of the lead devs:
"it may be better to have these features NOT accessible to the screnreader[sic] at all (which means they are effectively removed from the UI), because there is no point in presenting a feature that a person cannot use"
Along with a suggestion to implement a half-assed, blindness-specific GUI with half the features later down the thread.
The whole discussion is here, for those brave enough to read it https://github.com/prusa3d/prusaslicer/issues/7595
@arfs6@hachyderm.io@NoahCarver @miki My key take on this is specialized solutions for blind people has been tried earlier and it didn't end up well.
An example of this is edbrowse.
I have been thinking; A specialized solution might unlock more capabilities. The argument against the idea is it becomes difficult to maintain. Well, I have no experience here.
I'll think more on this and perhaps right a blogpost about it.