thunderbird / thunderbird/thunderbird-android
Talkback screen reader can't read some messages
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App
Thunderbird for Android
App version
8.1
Where did you get the app from?
Google Play
Android version
14
Device model
Samsung Galaxy A54
Steps to reproduce
- open Thunderbird with Talkback enabled; 2. open a message; 3 swipe to the right 9-10 times to move the focus to the web views which containse the text of the message. Sometimes the screen can't read the message and announces "no next default element".
Expected behavior
The screen reader should read the text of the message like in other apps.
Actual behavior
The screen reader says: "no nex default element".
Logs
I am a blind Android user on a Galaxy A54 with Android 14. It happens that when scrolling through an open message with the appropriate gestures of the Talkback screen reader, the text content in the web view is sometimes not spoken. The screen reader announces something like: "no next default element". This happens both when using swipes to move to the next element or paragraph, and when using the continue reading command. A sighted person told me that in some messages, when this problem occurs, a few characters per line or one or two words are shown. The problem occurs sometimes when opening messages one at a time, other times when scrolling to the next message with two fingers, but having disabled the Thunderbird scrolling gestures. Sometimes, but not always, closing the message and reopening it is possible to read it. I have not detected a regularity in the occurrence of the problem or even a specific type of message in which this happens more frequently, except perhaps the very long ones. It can happen that I can read many messages before the screen reader can't read the content, but sometimes it's two or three messages in sequence that aren't read. The other parts of the screen in a message are read correctly and it's only the web view that gives problems. The app is very good for me and could replace the others I use as an alternative, but unfortunately I can't rely on it for now. I hope it can be solved even if I'm not sure I've provided enough information. Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the problem in Thunderbird for Android 8.1 with TalkBack enabled, focusing on the web view that contains message text. Compare affected and readable messages, including long messages and reopening a message. Done means TalkBack consistently reads the message content while moving through it or using continuous reading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- accessibility, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100