Follow

So it looks like neither Firefox nor Chromium are accessible under GNOME (silence on the screen reader). What’s worse, it doesn’t appear that Overview mode is accessible (tested on Pop!_OS). You cannot use the search on it (e.g., type software – the s disabled speech).

Does anyone know where these issues are being discussed?

@aral People are definitely talking about accessibility issues on gitab.gnome.org @ gitlab.gnome.org/search?group_ (and there are quite a few merge requests pending too).

For centralized a11y discussions, there's gnome-accessibility-list and gnome-accessibility-devel mailing lists and #a11y on irc.gnome.org. More details @
wiki.gnome.org/Accessibility

And, of course, there's the Orca repo on GNOME's gitlab. That's probably a good place for general screen-reader issues: gitlab.gnome.org/GNOME/orca/is

@aral Also, Firefox and Chromium probably interact with Orca differently under X11 versus Wayland (and native Wayland apps vs X11 apps on Wayland too).

Using the X11 versions on X11 is most likely the best combo for now, due to the length of time it's been around. Hopefully Wayland will keep getting better a11y support as time progresses.

@aral I just asked about this on birdsite too; hopefully someone jumps in with some good news. twitter.com/garrett/status/113

@garrett That would make sense. Sadly, I’m seeing this behaviour under X11. Haven’t tested with Wayland yet.

@aral Last time I tried, the onscreen keyboard also didn't work with Firefox and Chromium. Maybe it's related?

@aral There's a possibilty it works on X11 but not Wayland.
(If it's broken in general, and then fixed, it might still not work on Wayland, as it is very restrictive on grabbing content, but I could also be wrong about how that screen reader works)

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.