VoiceOver reads unclear messages in Themes section of the Create/Edit pages
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox133 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | disabled |
firefox136 | --- | disabled |
firefox137 | --- | verified |
People
(Reporter: sbadau, Assigned: cmkm)
References
(Blocks 4 open bugs)
Details
(Keywords: access, Whiteboard: [fidefe-profile-management])
Attachments
(2 files)
Found in
- Nightly 135.a1
Affected versions
- Nightly 135.a1
Tested platforms
- Affected platforms: macOS 15
Preconditions
- Ensure that the pref "browser.profiles.enabled" is set to true in about:config.
- Create at least one profile.
- Enable Voice Over Screen reader.
Steps to reproduce
- Use VoiceOver to navigate to the Profiles panel from the Hamburger menu.
- Use VoiceOver to enter Edit mode.
- Navigate to the Themes section and focus on a theme using VoiceOver.
Expected result
- The user should be informed by VoiceOver that they can select a specific theme from the provided list.
Actual result
- The message provided by VoiceOver is unclear. Initially, it reads: "Article, you are currently in an Article." Moving forward, VoiceOver announces "Image," followed by the theme name. Please see the attached screen recording with sound for more details.
Regression range
- This is not a regression; it's introduced with the Profiles Switching feature.
Additional notes
- The same behavior is encountered on both the about:editprofile and about:newprofiles pages.
Updated•2 months ago
|
Comment 1•2 months ago
|
||
Access s2 because:
- The image has no alt attribute.
- The theme items provide no semantic indication that they are selectable; e.g. role="button". A proper listbox pattern would probably be better, but that will also require keyboard navigation work.
- The theme items provide no semantic indication as to whether they are selected or not.
Comment 2•2 months ago
|
||
The severity field is not set for this bug.
:mossop, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 months ago
|
Comment 3•1 month ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:mossop, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Assignee | ||
Updated•22 days ago
|
Assignee | ||
Comment 4•15 days ago
|
||
Comment 6•9 days ago
|
||
bugherder |
Comment 7•9 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 8•8 days ago
|
||
The patch landed in nightly and beta is affected.
:cmkm, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox136
towontfix
.
For more information, please visit BugBot documentation.
Comment 9•8 days ago
|
||
Limited to nightly only so does not need a beta uplift
Reporter | ||
Comment 10•1 day ago
|
||
Verified as fixed using the latest Nightly 137.0a1 (Build ID: 20250213205200) on macOS 15 and VoiceOver - the theme names are now read, there is an indication that the themes are selectable, and the selected theme is announced correctly.
Description
•