It bothers me quite a lot that in the `ariaNotify` explainer, relating to a more robust mechanism for web apps to fire #screenReader messages, #braille is demoted to a "future consideration". Even there, it's listed under a heading of "Braille and speech markup", as though it doesn't even warrant a devoted section of its own.
Braille being treated with the same priority of speech is long overdue. We're clearly not there yet.
github.com/MicrosoftEdge/MSEdg…
#accessibility
MSEdgeExplainers/Accessibility/AriaNotify/explainer.md at main · MicrosoftEdge/MSEdgeExplainers
Home for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainersGitHub
reshared this


Pitermach
in reply to Onj 🎶 • • •Onj 🎶
in reply to Pitermach • • •@pitermach It's using Juce, but with a lot of unlabelled buttons. They do know about it, as I had a meeting with them this morning and was able to screen-share and let them know that lots of stuff doesn't work.
It seems that they're using the Ujam libraries, so it's up to Ujam to modify their code to allow accessibility, but they can pass this feedback to them.
Rodes also use the same framework.
If you've got any libraries where the main sample content uses the .blob format, then you've used Ujam's UI's.
Pitermach
in reply to Onj 🎶 • • •Onj 🎶
in reply to Pitermach • • •Onj 🎶
in reply to Pitermach • • •Zach Bennoui
in reply to Onj 🎶 • • •Onj 🎶
in reply to Zach Bennoui • • •Zach Bennoui
in reply to Onj 🎶 • • •Rebecca Legowski
in reply to Onj 🎶 • • •The last time I used that, I had to get a remote session with them about it.
Zach Bennoui
in reply to Rebecca Legowski • • •Rebecca Legowski
in reply to Zach Bennoui • • •Zach Bennoui
in reply to Rebecca Legowski • • •