Re: [orca-list] Accessibility broken under Wayland Fedora 31

[Jason White <jason jasonjgw net>]

On 11/4/19, 16:42, "orca-list on behalf of Samuel Thibault via orca-list" <orca-list-bounces gnome org on 
behalf of orca-list gnome org> wrote:

    Not everybody there think like that. Some are fine with having some
    support, but see some pieces of it as ugly hacks, and I can only agree:
    keyboard snooping and synthesis are very problematic. Discussions around
    FOSDEM should help to sort the situation out.
    
That's encouraging news. According to a Fedora-related interview in a recent Linux Unplugged podcast:
https://linuxunplugged.com

XWayland will become optional in a future Fedora release. I would not be surprised if other Linux 
distributions follow. To be specific, XWayland will only be run if an application needs it.

Pipewire is intended to support both low-latency applications that use Jack for audio, and applications that 
use PulseAudio. In sum, it replaces the server (daemon) side of both Jack and PulseAudio. What isn't clear to 
me is whether Pipewire will also address the perennial problems of audio routing on Linux systems (e.g., 
using Orca alongside a console-based screen reader).

Pipewire also supports remote desktops under Wayland - as yet, so far as I am aware, without any 
accessibility support that would enable braille or speech-based access to a remote desktop.

In the same interview, it is noted that user research is underway toward defining requirements for GNOME 
Shell 4. I don't know whether users with disabilities are included in that process, however.