Earlier quoted context omitted.
I have my opinion on aesthetics of additional ways of repeating information already available by color coding. But to each their own. Other than that, is enabling/disabling any of the aforementioned features ever a question of aesthetics?
For example, opting to not enable high-contrast mode is a question of aesthetics. Arguably reading text would become easier for the user, but they prefer to sacrifice a little of the readability in favor of looks.
GUIs should be fully keyboard-driven
521–527 of 527 posts
Re: GUIs should be fully keyboard-driven
#522Earlier quoted context omitted.
> showing the relevant keyboard shortcuts in the UI can be overwhelming Underlining the accelerator key is subtle and shouldn't be overwelming. Keyboard navigation unaware users probably won't even notice.
This works poorly if you intend to localise your application. Great if you don't though.
Re: GUIs should be fully keyboard-driven
#523Earlier quoted context omitted.
> accessibility is just usability. all it is is making sure your product is as usable by as many people as possible. Not always. There are things that increase usability for fully abled people but decrease it for disabled people. Color-coding is a common one. Another is using smaller font size to make more info visible at once, or advanced touch gestures that can be accidentally triggered by shaky hands. Then there a…
> Another is using smaller font size to make more info visible at once This doesn't sound very usable to me.
Re: GUIs should be fully keyboard-driven
#524Earlier quoted context omitted.
once again, I get to cite the IBM AS/400 CallPath system demonstrated here https://youtu.be/5pY6Xxptp9A?t=2083 which almost brought a tear to at least one viewer's eye
Pretty cool video. I would love to know more about the internal design of the as400 platform and how people thought and designed user interfaces. I can't shake the feeling that these interfaces are so lean they're satisfying. Also, I feel that a lot of interfaces today are wasting resources.
Re: GUIs should be fully keyboard-driven
#525Earlier quoted context omitted.
Dlangui is so niche that I am amazed to even see it here. DearImGui is intended for thowing together some slap-dash UI widgets for debugging things like interactive rendering. Do Qt built-in widgets have huge problems? Inwould assume that custom widgets invariably do because approximately nobody writes any accessibility handling for them.
> Dlangui is so niche that I am amazed to even see it here. Eh, I'm testing whether I can make it fully accessible, since I happen to like the D language itself. But the UI without my changes is entirely inaccessible. > DearImGui is intended for thowing together some slap-dash UI widgets for debugging things like interactive rendering. That's probably what it's intended for, but people use it for far more than that,…
Re: GUIs should be fully keyboard-driven
#526Re: GUIs should be fully keyboard-driven
#527Earlier quoted context omitted.
This is where using a common framework pays dividends. For example, on the desktop I can disable animations for all GTK applications.
I stopped using GNOME after 3, but there were still quite a few animations in the GNOME core programs despite having the disable animation setting set. I wonder if that's changed.