Live data from Hacker News

A small change to improve browsers for keyboard navigation

b.43z.one

71–72 of 72 posts

Re: A small change to improve browsers for keyboard navigation

#71
Honestly, most sites these days built in such incompetent way I cannot imagine how much disabled users suffer...

Since there is no tariff adding in react code, even my teammates are using these as pseudo buttons. As a user, I cannot even tell if it's a button or not. The cursor usually doesn't change or becomes "I-beam" (text selection). Only way to understand is click random places and wait for mysterious stuff to happen.

Re: A small change to improve browsers for keyboard navigation

#72
post #68

Earlier quoted context omitted.

This delay is configurable. The delay is there so you can actually type a bit before the UI pops up, and then the UI will be filtered to just your selection.

The configuration lies. Even with "Show hints" set to "Immediately", there is a long delay. Feels like half a second on M1 Pro.

Fair, fair—it's default is longer, so dialing it down made it feel zippy by comparison.

I'm trying out Homerow and I'm really liking it! Thanks for mentioning it. I might end up sticking with it actually.

Post reply on HN