jamulussoftware / jamulussoftware/jamulus

Accessibility: Chat History is not properly accessible with Screen Reader

Open
#3,613 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C
Stars
1.1k
Forks
248
Avg merge
2d 3h
Merged PRs (30d)
9

Description

Not sure whether this is another Qt bug with QTextBrowser, but VoiceOver cannot navigate the chat history (txvChatWindow) reliably, especially when there is a long message.
When you press the up or down arrow in the chat history and VoiceOver encounters a long entry (for example, a server intro message), it seems to treat the text as multiple wrapped lines, but it only reads the first few words in the beginning. After that, navigation through the rest of the history becomes broken.
Is it possible to present each chat entry as a separate accessibility element instead of one large block of text within the QTextBrowser? That might resolve the issue.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in txvChatWindow with VoiceOver, including a long chat entry, and inspect how the QTextBrowser exposes wrapped text. Determine whether each chat entry can be presented as a separate accessibility element. Done means VoiceOver can navigate the full history reliably and read long entries completely.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.