For Firefox and surely for Chrome and Safari aswell, there are vim extensions.
I have one, it’s beautiful and wouldn’t want to miss it.
GUIs should be fully keyboard-driven
351–360 of 513 posts
Re: GUIs should be fully keyboard-driven
#352I work on ADA a lot for my company. Please put on some headphones, turn on the voice assistant of your OS, put on some blinders, and run your app or website… no mouse, just keyboard. 1. Democracy is about access; make sure everyone has access to your software. 2. The keyboard allows folks with disabilities and power users to fly through your website/app… that being said… the second a tab is off, the person with a dis…
Also, please avoid animations and transitions, or at least add a button to reduce them.
This is where using a common framework pays dividends. For example, on the desktop I can disable animations for all GTK applications.
Re: GUIs should be fully keyboard-driven
#353Earlier quoted context omitted.
That's because at the end of the day: - accessibility is just usability. all it is is making sure your product is as usable by as many people as possible. - it's a myth that "people with disabilities" are some other that excludes you, and 'accessibility' or assistive technologies only benefits other people . Everyone is only temporarily 'abled'. You need to use prescription glasses to comfortable read a computer scre…
> 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…
Colors should be an OS feature. On iOS and macOS you can remap colors globally and it works in all native apps. There are presets fire the common cases: red/green issues, color blindness etc and you can make your own. This has its limitations though eg if you are not able to distinguish at least 5 or so colors… any colors.
Re: GUIs should be fully keyboard-driven
#354I work on ADA a lot for my company. Please put on some headphones, turn on the voice assistant of your OS, put on some blinders, and run your app or website… no mouse, just keyboard. 1. Democracy is about access; make sure everyone has access to your software. 2. The keyboard allows folks with disabilities and power users to fly through your website/app… that being said… the second a tab is off, the person with a dis…
I have a traditional desktop app/GUI app, where I have a table (treeview) of words with their translations and pronunciation (like a dictionary). There can be thousands of words in there. Also there is a filter/search field, where one can input any string to filter the table while typing, or confirming pressing enter/return. The words in the table can be in any language, if the configuration of the application is adjusted to the language.
How would I make this more accessible for the blind or people with bad vision?
Re: GUIs should be fully keyboard-driven
#355I work on ADA a lot for my company. Please put on some headphones, turn on the voice assistant of your OS, put on some blinders, and run your app or website… no mouse, just keyboard. 1. Democracy is about access; make sure everyone has access to your software. 2. The keyboard allows folks with disabilities and power users to fly through your website/app… that being said… the second a tab is off, the person with a dis…
I had to keep accessibility in mind a lot in my previous job (web development for a university). The thing that I consistently found was that, the more accessible a website was, the better the experience for everyone , not just people with disabilities.
Additionally, I found, that simply sticking to web standards, instead of reimplementing everything in JavaScript, goes a long way towards accessibility.
Re: GUIs should be fully keyboard-driven
#356A game changer for me was the link hints extension on firefox and chrome: instantly enabled a lot of websites to be keyboard-driven.
Re: GUIs should be fully keyboard-driven
#357Earlier quoted context omitted.
That's because at the end of the day: - accessibility is just usability. all it is is making sure your product is as usable by as many people as possible. - it's a myth that "people with disabilities" are some other that excludes you, and 'accessibility' or assistive technologies only benefits other people . Everyone is only temporarily 'abled'. You need to use prescription glasses to comfortable read a computer scre…
> 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…
But you can — or should be able to — independently toggle all of those features. For example, the app should work in high-contrast mode with disabled color coding, it should work with touch gestures disabled, etc.
A good common framework helps here. Then, it's up to each user to set their settings properly.
Re: GUIs should be fully keyboard-driven
#358Earlier quoted context omitted.
I think you vaaastly overestimate how excel is used by most users if anything, excel exceeds in being MOUSE-driven - it's intuitive in what you press and what you drag and that's kinda my problem with the TFA - author is not representative of typical user. Mouse interaction is the king
Basically everyone in a white collar job who is NOT a developer is using Excel. I'm a developer, even I have to use Excel at work.
that's exactly what I'm saying
basically everyone uses Excel. And basically everyone is a MOUSE-first user (or, even further along the chain: TOUCHSCREEN-first)
keyboard-based menu navigation is not intuitive. it can be "poweruser" oriented, but it's not for most of the userbase
Re: GUIs should be fully keyboard-driven
#359Earlier 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…
Colors should be an OS feature. On iOS and macOS you can remap colors globally and it works in all native apps. There are presets fire the common cases: red/green issues, color blindness etc and you can make your own. This has its limitations though eg if you are not able to distinguish at least 5 or so colors… any colors.
That's why you don't just use colour for identification. E.g. include a warning icon next to a button/element in addition to using a warning colour.
Re: GUIs should be fully keyboard-driven
#360[flagged]