4 ms·
That's the hill that almost every new UI toolkit effort dies on. If I were going to start one, I would actually start with accessibility. If everyone keeps tri
by api 4y ago
That's the hill that almost every new UI toolkit effort dies on.
If I were going to start one, I would actually start with accessibility. If everyone keeps tripping over the same thing, start by tackling that thing first.
Edit: it's occurred to me that an approach of starting with accessibility could also lead to an approach that degrades gracefully into text UIs (TUI) and command line usage and then scales all the way up to a GUI. That would be super interesting. Not sure it's ever been done.
- mrlemke 4y agoI've been thinking about something similar. A polyvalent UI with CLI, GUI, and AUI (audible user interface). The AUI could be implemented as a TUI/HTML page (to leverage existing work on screen readers) but designed to be read rather than seen.
- andydotxyz 4y agoThe behaviour based api that Fyne is designed with will degrade to a text UI, if anyone implements that driver ;). I always thought I would but it’s never reached high on priorities…
- carapace 4y agoShout it from the hills: OXO! (As in the easy-to-use kitchenware https://en.wikipedia.org/wiki/OXO_(kitchen_utensils_brand) https://en.wikipedia.org/wiki/OXO_(kitchen_utensils_brand) "In June 2004, Helen of Troy Limited bought OXO housewares for $273.2 million.") It's a general pattern, make your thing easy for old people and folks with disabilities and it's also easy for everybody else. - - - - Check out Elm's accessible-html module. Enforces accessibility at compile-time. https://package.elm-lang.org/packages/tesk9/accessible-html/latest/ https://package.elm-lang.org/packages/tesk9/accessible-html/... https://dev.to/nimmo/easier-paths-to-accessibility-in-elm-4ojo https://dev.to/nimmo/easier-paths-to-accessibility-in-elm-4o...