While typing in the address bar, it's impossible to explore its content with a screen reader
Categories
(Firefox for Android :: Search, defect)
Tracking
()
| Accessibility Severity | s2 |
People
(Reporter: csadilek, Unassigned)
References
Details
(Keywords: access, Whiteboard: [fxdroid][group3][s2-2025])
From github: https://github.com/mozilla-mobile/fenix/issues/20491.
Steps to reproduce
- Open Firefox with TalkBack enabled.
- Tap the address bar and start typing.
- Try to explore the typed text via TalkBack navigation gestures (characters, words, etc.).
Expected behaviour
- While typing, TalkBack should repeat the characters as they're being typed,.
- After typing a word followed by a space, TalkBack should read the typed word.
- one should be able to explore typed text as well as URLs using TalkBack navigation gestures (characters, words, etc.).
Actual behaviour
- Character echo while typing doesn't work.
- Word echo while typing doesn't work.
- It's impossible to explore the actual Tex in the address bar with TalkBack gestures.
Device name
Xiaomi Redmi Note 8
Android version
MIUI 12.0.4.0, Android 10
Firefox release type
Firefox Nightly
Firefox version
92.0a1 (Build #2015823243) AC: 92.0.20210719094322, 97d95e60fb GV: 92.0a1-20210718090829 AS: 79.0.0
Device logs
No response
Additional information
TalkBack version 9.1
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•1 year ago
|
||
This feels like an access-s2 because this is an expected behavior that allows users of screen readers to more conveniently review the value of the input without a need to navigate back and forth in the field and helps users with cognitive difficulties and dyslexia to have less strain while using these inputs.
Comment 3•1 year ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:skhan, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Comment 4•1 year ago
|
||
Since Bug 1931940 has been filed, I'd like to bring attention to this important issue that doesn't appear to be fixed with the new toolbar.
I'm requesting info from who appears to be the engineering lead. An apology if I should have pinged someone else.
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Description
•