Mastodawn

I was helping an open-source app become more #accessible yesterday and we ran into the problem that it looks like #screenReader Orca has a bit of a tendency to crash when exposed to webkitGTK applications. I've not done Desktop #linux for a long time and have no idea what the workarounds for this would be, does anyone know anyone who might know what's happening here? Do we need to set a random environment variable somewhere or update a specific package so this person can do basic screen reader testing on their app? #tech #openSource #screenReaders #linux #GTK #webdev

Show thread

Peter Vágner Mar 31

@zersiax It looks as compared to firefox or chromium webkit gtk has some issues when it comes to screen reader accessibility.
Sometimes the focus is trapped in some unlabelled object, accessible labels from multiline children only take first line into account.
In v 2.50.6 an important issue related to incorrect role types being reported has been fixed.

For example all the tauri based apps are suffering from webkitgtk issues no matter how much great screen reader accessibility has been put into their design.

Show thread

Florian Mar 31

@pvagner yep, this is a Tauri app. Is specifically that issue currently being worked on, that you know of?

Show thread

Peter Vágner Mar 31

@zersiax I'm afraid no ongoing accessibility related work for webkitgtk is in in progress currently.

That being said I am not involved I'm just a linux user watching some email lists and people on mastodon and these are my guesses.

Show thread

Tamas G

@pvagner @zersiax oh boy I really hope that's not true but with how slow Webkit bugs get resolved I wouldn't be surprised. VoiceOver is always the hardest one to rangle into submission for me especially where elements with complex parent-child relationships are involved and specific widget rules it just doesn't honor the same.