[Win] Screen reader does not read the exceptions checkboxes on Beta
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | affected |
People
(Reporter: cgeorgiu, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Mandatory template
Found in
- Beta 140.0b3
Affected versions
- Beta 142.0b3
- Nightly 143.0a1
Tested platforms
- Affected platforms: Win 11
- Unaffected platforms: macOS 15 and Ubuntu 24.04
Steps to reproduce
- Go to about:preferences#privacy.
- Select Strict mode from ETP section.
- Click on the "Allow Firefox to automatically apply exceptions required to avoid major website breakage" checkbox.
- Press the space button from the keyboard.
Expected result
- Checked is announced by the screen reader.
Actual result
- The voice over does not read the checkbox status.
Regression range
- This seems to be an issue specific to the Beta build, as I was not able to reproduce it on Nightly.
Additional notes
- I've tested with Winnows built-in screen reader, Narrator.
|
||
Comment 2•6 months ago
|
||
Hey Ciprian, I have tested this on beta which seems to be broken, and on nightly which is fixed. However in beta, I tested all the other checkboxes and doesn't seem like any of them are saying "checked"/"unchecked" either? Maybe this is a known issue fixed in Beta?
|
||
Updated•6 months ago
|
|
Reporter | |
Comment 3•6 months ago
|
||
(In reply to Leo Liu [:leoliu] from comment #2)
Hey Ciprian, I have tested this on beta which seems to be broken, and on nightly which is fixed. However in beta, I tested all the other checkboxes and doesn't seem like any of them are saying "checked"/"unchecked" either? Maybe this is a known issue fixed in Beta?
Indeed, I can reproduce the issue with other checkboxes on the "about:preferences" page as well. It appears to be a general screen reader issue, rather than something specific to this feature.
|
||
Comment 4•6 months ago
|
||
This is specific to narrator, which uses UI Automation. It is fixed by our native UI Automation implementation which is currently enabled on Nightly but not yet in beta or release. We're hoping to do a controlled rollout to beta and release in 143.
Description
•