https://bugs.kde.org/show_bug.cgi?id=526978
Bug ID: 526978
Summary: KDE Connect Windows app: navigation drawer handle has
no accessible name, so screen reader users cannot open
the device list
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: windows-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 197034
--> https://bugs.kde.org/attachment.cgi?id=197034&action=edit
KDE Connect for Windows - UI Automation tree (what NVDA sees)
***
# Bugzilla report (kdeconnect / windows-application)
## Summary
KDE Connect Windows app: navigation drawer handle has no accessible name, so
screen reader users cannot open the device list
## Comment
KDE Connect for Windows (Qt Quick / Kirigami, Qt 6.11.1) is hard to use with
the NVDA screen reader. In the Windows UI Automation tree - the data NVDA reads
- the control that opens the navigation drawer / device list is exposed as a
Button with an EMPTY accessible Name, and several core containers expose only
generic Group/Pane roles. A screen reader user therefore cannot find or
activate the drawer handle to reach the device list, which makes the app
largely unusable.
STEPS TO REPRODUCE
1. Start NVDA.
2. Launch KDE Connect for Windows 26.08.1.
3. Move focus through the main window (or inspect the UI Automation tree of the
main window).
OBSERVED RESULT
- The navigation drawer handle is exposed as a Button with an empty Name.
- Only some welcome-page text/buttons are named; the drawer handle and other
structural controls are unnamed.
EXPECTED RESULT
- Every interactive control exposes a Name and Role; the drawer handle should
announce something like "Open drawer" / "Close drawer" (matching its existing
tooltip).
ADDITIONAL INFORMATION
- Attached: kdeconnect-uia-tree.txt - the live UI Automation tree of the app
(captured per the KDE accessibility guide).
- Related: bug 509710 (plugin settings accessibility, still open), bug 517006
(fixed). The pairing PlaceholderMessage texts now announce via Kirigami's
Accessible.announce, so the FIXME comments in DevicePage.qml appear stale.
VERSIONS
- KDE Connect: 26.08.1
- Qt: 6.11.1
- NVDA: 2026.2
- OS: Microsoft Windows 10 Home [10.0.19045]
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Do not paste LLM output.
Please remove this comment after reading and before submitting - thanks!
***
DESCRIPTION
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
KDE Connect for Windows (Qt Quick / Kirigami, Qt 6.11.1) is hard to use with
the NVDA screen reader. In the Windows UI Automation tree - the data NVDA reads
- the control that opens the navigation drawer / device list is exposed as a
Button with an EMPTY accessible Name, and several core containers expose only
generic Group/Pane roles. A screen reader user therefore cannot find or
activate the drawer handle to reach the device list, which makes the app
largely unusable.
STEPS TO REPRODUCE
1. Start NVDA.
2. Launch KDE Connect for Windows 26.08.1.
3. Move focus through the main window (or inspect the UI Automation tree of the
main window).
OBSERVED RESULT
- The navigation drawer handle is exposed as a Button with an empty Name.
- Only some welcome-page text/buttons are named; the drawer handle and other
structural controls are unnamed.
EXPECTED RESULT
- Every interactive control exposes a Name and Role; the drawer handle should
announce something like "Open drawer" / "Close drawer" (matching its existing
tooltip).
ADDITIONAL INFORMATION
- Attached: kdeconnect-uia-tree.txt - the live UI Automation tree of the app
(captured per the KDE accessibility guide).
- Related: bug 509710 (plugin settings accessibility, still open), bug 517006
(fixed). The pairing PlaceholderMessage texts now announce via Kirigami's
Accessible.announce, so the FIXME comments in DevicePage.qml appear stale.
VERSIONS
- KDE Connect: 26.08.1
- Qt: 6.11.1
- NVDA: 2026.2
- OS: Microsoft Windows 10 Home [10.0.19045]
--
You are receiving this mail because:
You are watching all bug changes.
