Accessibility: Implement Chat List Navigation and Subsection Context Announcements for Screen Readers #30173
Conversation
|
|
|
I think you guys need to cooperate somehow with @rezabakhshilaktasaraei, he started pushing first accessibility changes for tdesktop and currently has the next PR for chats list as well. My comment to his PR was: That requires a lot of thinking through. It's nice that it could be done at least in principle, but currently its very invasive and I'm not sure about lifetimes, that it won't crash or leak. I'll try to read this through / review / think how it could be done, but I'm not sure when exactly. The same could be said about this suggestion. I'm yet to understand how this should be done properly and least invasive and with better code foundation for future changes (for messages list etc). We can make a group in Telegram with accessibility support discussion, so that the same work isn't done separately in vain. |
a20f59e to
a5bb096
Compare
|
Hello @john-preston, Zendalona (including @mukthar777) is ready to collaborate with @rezabakhshilaktasaraei on this. |
|
@john-preston Understood. I am very interested in contributing further to this foundation and agree on the importance of a unified accessibility framework. I look forward to joining the Telegram group to coordinate our efforts: https://t.me/musthafal_mukthar |
This Pull Request enhances the screen reader accessibility of the chat list and its associated subsections. By implementing native accessibility interfaces, the application now provides accurate contextual feedback during navigation, specifically announcing the current chat name and its related metadata (such as unread counts and last message content) while traversing the list in both Default and Filtered states."
Technical Details