I very much agree with @yatil here. There simply is no reason why a very common design pattern like a toolbar container should not be part of HTML, and browsers implement the proper keyboard interaction. Or why on Earth HTML still doesn’t have rich list box items or tree views / tree tables.

Because both many web developers and browsers still let blind people down regularly, JAWS still wants access to the full HTML in modern browsers so they can fix up most common errors, and even allow script authors to more finely tune the experience if they want to. For other purposes, GreaseMonkey and custom scripts for web sites to improve the accessibility are quite common in some circles. Basically, right now, the burden for a better accessible web lies on the screen readers and tech savvy blind coders who are able to script web sites via GreaseMonkey to improve the experience. JAWS has done this since 1999. And they’re not going to stop anytime soon.

https://yatil.net/blog/accessibility-action

@Marco

Advertisers See Elon Musk As A Liability As They Avoid Twitter by Mike MasnickMike Masnick

Elon Musk keeps talking about how he’s saving Twitter, but it’s difficult to see how. He’s made the site much more unstable, has been messing up basically every part of “trust & safety 101,” is now facing a growing number of lawsuits (including many over unpaid bills), has no idea how the site actually works, […]