Why in the fuck is it so hard to see buttons when kb selecting with tab in a browser? It's like:

"Tab....Tab.....Tab Tab Tab... oops, went too far,
Shift + Tab, Shift + Tab.... fuck!, too far left.. wait, is that button actually highlighted, oh it is too, wtf."

It's 2019, why is this still a thing?

You could try installing a Vim plugin. They let you target individual buttons. Using Tab is a major pain in the ass in comparison.

Just use vimium

esc, f, aj

Because many webdevs have absolutely no competence at all with regard to accessibility. Or web development in general.

@Fast-Nop well and also management kicks it way down the list knowing they won’t get hit unless they are a government entity or very large corp

@jeeper I once read an interesting interview where a shop owner said he made his crap accessible not because he wanted to make the world a better place or so.

Nah, it's because disabled folks also have money, and they want to buy shit on the internet even MORE so than normal folks. He just wanted their money that his competitors threw away, means he had to make his shop so that they were able to throw their money at him.

We need a tree-like system to select stuff. Like, on a search results page up/down navigate hits, one layer below they navigate various options for the card.
But the standard navigation system is one-dimensional even though data is almost never, so it will remain a PITA.

From myself 1 year ago, to me:

<!-- do not get ready of this if you want to be sane -->
</div>

@Nanos

Yeah that really grinds my gears