Skip to content

Announce selecting and deselecting a message - #31171

Open
rezabakhshilaktasaraei wants to merge 1 commit into
telegramdesktop:devfrom
rezabakhshilaktasaraei:message-selection-announcement
Open

Announce selecting and deselecting a message#31171
rezabakhshilaktasaraei wants to merge 1 commit into
telegramdesktop:devfrom
rezabakhshilaktasaraei:message-selection-announcement

Conversation

@rezabakhshilaktasaraei

@rezabakhshilaktasaraei rezabakhshilaktasaraei commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Pressing Space on a message, or extending the selection with Shift and the arrows, changes the selection without a screen reader saying anything about it.

The change was reported with a state change event carrying the selected flag. That flag is right as a "this is what changed" mask, but the Windows bridge reads only the checked flag out of a state change (qwindowsuiamainprovider.cpp, notifyStateChange), so nothing came out of it. Both message lists now also raise the selection event that does reach a screen reader; the state change is kept for the platforms that do read it.

Needs desktop-app/lib_ui#345 for accessibilityChildSelectionChanged().

Tested with NVDA on Windows 10: selecting a message announces "selected", deselecting it announces "not selected", and the same holds for the messages a Shift+arrow range grows over or gives back.

Space on a message, and Shift with the arrows, changed the selection
without a screen reader saying so: the change was reported through a
state change event, which the Windows bridge reads only the checked flag
out of. Raise the selection event that does reach it, telling apart a
message that just became selected from one that stopped being.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant