Open Bug 1583826 Opened 5 months ago Updated 3 months ago

Windows Narrator not working on Tracking Protection Panel

Categories

(Firefox :: Disability Access, defect, P3)

Desktop
Windows
defect

Tracking

()

Tracking Status
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- fix-optional

People

(Reporter: atrif, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Affected versions

  • 70.0b9 (20190923154733)
  • 71.0a1 (20190925095053)

Affected platforms

  • Windows 10x64

Preconditions

  • Narrator enabled (Go to Settings > Ease of Access > Narrator and then turn on the toggle under Use Narrator)

Steps to reproduce

  1. Open Firefox and a random website.
  2. Press Ctrl + L and Shift + Tab and Space to open the Tracking Protection Panel.
  3. Use up/down keyboard arrow keys to navigate.

Expected result

  • All items are correctly read by Windows Narrator.

Actual result

  • “No item in view” is read by the screen reader.

Regression range

Additional Notes

  • Using Tab key to navigate in Tracking Protection Panel makes the screen reader selector jump on the Taskbar.
  • NVDA screen reader is correctly working.
Has Regression Range: --- → yes
Has STR: --- → yes

Marco, what do you think about this? :)

Flags: needinfo?(mzehe)
Regressed by: 1572641

AFAIK, Narrator does not officially support Firefox yet. They need to use what they call an UIA to IAccessible2 bridge to get all the information they need from Chrome and Firefox, but thus far have only officially documented supporting Chrome. Narrator does not seem to recognize that these panels now use a document'ish interface. One could try pressing NarraotKey+Space to force Scan mode (what they call it), but since the UIA to IA2 bridge probably doesn't work in Firefox yet, this is very like to not work.

Again, Microsoft does not officially support Firefox with Narrator, so there are expected to be bugs like this that other screen readers that do support Firefox, don't exhibit.

Flags: needinfo?(mzehe)

Ok, thanks, that's, uh, a P3 then? Not really actionable for us at this point but would seem strange to just close it, too.

Priority: -- → P3
Component: Tracking Protection → Telemetry
Product: Firefox → External Software Affecting Firefox
Version: Trunk → unspecified

The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Priority: P3 → --

Wrote to our discuss list with Microsoft and got this answer from Gov.

You would just need to implement the UI Automation provider:
https://docs.microsoft.com/en-us/windows/win32/winauto/entry-uiauto-win32?redirectedfrom=MSDN

So, it might be actionable for us after all.

Flags: needinfo?(jhofmann)

Ah, thanks for getting in touch with them, but that seems like something the a11y team would need to build and maintain, not something for security engineering.

Janet, I'm not sure why you moved this to Telemetry, but I'm moving it back to Firefox.

Component: Telemetry → Disability Access
Flags: needinfo?(jhofmann)
Product: External Software Affecting Firefox → Firefox

The priority flag is not set for this bug.
:asa, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(asa)
Flags: needinfo?(asa)
Priority: -- → P3
Version: unspecified → Trunk

Unassigned and P3, marking as fix-optional in case a safe upliftable fix materializes in the next couple weeks.

You need to log in before you can comment on or make changes to this bug.