https://bugs.kde.org/show_bug.cgi?id=507545
Bug ID: 507545
Summary: Issue: Orca screen reader does not announce Caps Lock
state in KDE Plasma Wayland sessions, causing
confusion for visually impaired users who rely on Caps
Lock as a modifier key (e.g., Caps Lock + U, Caps Lock
+ O). Expected Behavior: Similar to GNOME, Or
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Orca screen reader should announce Caps Lock state in KDE Plasma Wayland
session
Currently, when using the Orca screen reader in KDE Plasma under a Wayland
session, Orca does not announce whether Caps Lock is enabled or disabled. This
creates confusion for users who rely on Caps Lock as the Orca modifier key
(e.g., Caps Lock + U, Caps Lock + O for flat review navigation).
In GNOME, this issue is addressed through AT-SPI and AccessKit integration,
allowing screen readers to monitor modifier key states. KDE Plasma could
implement a similar mechanism via KWin or KGlobalAccel, enabling Orca to detect
and announce the Caps Lock state.
Suggested improvements:
1. Provide an API (e.g., via D-Bus or another method) that allows Orca to query
the current Caps Lock state.
2. Integrate this capability into KWin or the KDE Accessibility module.
3. Alternatively, expose a Wayland-compatible equivalent of
XkbGetIndicatorState to allow screen readers to access modifier key states.
This enhancement would significantly improve accessibility for visually
impaired users and reduce confusion when using Orca's keyboard shortcuts.
SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch linux
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
--
You are receiving this mail because:
You are watching all bug changes.
