Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-65520

No API for screen readers to receive keyboard events under a Wayland session

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • orca-48.0-1.el10
    • Yes
    • Important
    • rhel-display-tools-accessibility
    • ssg_display
    • 20
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • CentOS Stream, Red Hat Enterprise Linux
    • None
    • All
    • None

      In the times of GTK 3 or a X.Org session, Orca, the screen reader, could receive keyboard input basically however it liked.
      Under GTK 4 and a Wayland session, Orca does not receive any keyboard input from GTK 4 apps, because GTK 4 is no longer using the legacy keyboard notification API, and is not running under X.Org.
      As a result of that, no screen reader commands work in this context (user can not stop speech, can not access Orca settings, etc.). Probably the most annoying situation will occur in the terminal emulator, because the user can not use any screen reader commands to review the command input (so no word by word reading, no copying of only a part of the output, no reliable line by line review (scrolling the terminal view does not count as it is unreliable with a screen reader everywhere)).
      There's actually a discussion about a XDG desktop portal, which, if implemented, would allow fixing the situation, see https://github.com/flatpak/xdg-desktop-portal/issues/1046.

              ltyrycht Lukáš Tyrychtr
              ltyrycht Lukáš Tyrychtr
              Lukáš Tyrychtr Lukáš Tyrychtr
              Bohdan Milar Bohdan Milar
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: