1764103 - [Windows 10 x64] The “Thank you” spotlight modal is not correctly displayed when Narrator screen reader is used

Status: RESOLVED WONTFIX

(Firefox :: Messaging System, defect, P3)

Description

[Alice Varro [avarro], Ecosystem QA]

Attachment: Untitled1.mov

[Affected versions]:

• Firefox Beta 100.0b4 - Build ID: 20220410195727
• Firefox Nightly 101.0a1 - Build ID: 20220411094830

[Affected Platforms]:

• Windows 10 x64, version 21H1, OS build 19043.1586
• Windows 10 x64, version 21H2, OS build 19044.1586

[Prerequisites]:

• Have a Firefox Beta 99 installed.
• Have a new Firefox profile.
• Have the “Narrator” screen reader installed and opened.

[Steps to reproduce]:

1. Open the browser from prerequisites.
2. Update the browser to the latest version.
3. Observe the “Thank You” spotlight.

[Expected result]:

• The “Thank you” spotlight is correctly displayed and all the elements can be successfully accessed through the screen reader.

[Actual result]:

• The “Thank you” spotlight is being cut off on the left-hand side when the “Narrator” screen reader is active.

[Notes]:

• This issue is also reproducible after the Narrator screen reader is turned off.
• This issue is not reproducible using the NVDA screen reader.
• This issue is not reproducible on Windows versions <1903.
• Attached is a screen recording of the issue:

Comment 1

[Emily McMinn :emcminn]

I've brought this up with the a11y team, and the consensus is that we don't actually support Narrator, as it requires a framework which we haven't implemented (UIA). There is an open bug to eventually implement UIA that I will mark as blocking this; but until that's done this should be WONTFIX.

Comment 2

[James Teh [:Jamie]]

It's pretty weird that Narrator would cause the visual display of this modal to break without UIA being implemented, though. UIA does have a bridge to IAccessible2 (which we do implement), so my guess is that Narrator must be calling something (perhaps a scroll method) which breaks things here. I don't think there's any action until we look at UIA properly, but my guess is that even once implemented, there's going to be specific work to do here, probably related to scrolling edge cases.