Closed Bug 1790027 Opened 2 years ago Closed 2 years ago

The elements from the "about:home" page are read by the screen reader software while the Onboarding Modal is displayed

Categories

(Firefox :: Messaging System, defect, P1)

Desktop
Windows
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox104 --- unaffected
firefox105 --- unaffected
firefox106 --- affected

People

(Reporter: mcoman, Assigned: emcminn)

References

(Blocks 1 open bug)

Details

(Keywords: access)

[Affected versions]:

  • Firefox Nightly 106.0a1 - Build ID: 20220908213354

[Affected Platforms]:

  • Windows 10 x64

[Prerequisites]:

  • Have a screen reader software installed and enabled (E.G. NVDA, Windows Narator).
  • Have an older version of Firefox Nightly installed (E.G. Firefox Nightly 105.0a1).

[Steps to reproduce]:

  1. Open the browser with the profile from the prerequisites.
  2. Update the browser and observe the behavior.

[Expected result]:

  • The elements from the Onboarding modal for existing users are successfully recognized and read by the screen reader software.

[Actual result]:

  • The elements from the "about:home" page are read instead.

[Additional Notes]:

  • This issue is not reproducible with the VoiceOver software on macOS.
  • Attached a screen recording of the issue.
Priority: -- → P1
Assignee: nobody → emcminn
Keywords: access

I think this might actually be an NVDA bug. In my testing, the dialog did get focus correctly, but the reading of the page behind it (which loads first) was not interrupted. I don't think we can really work around this on our side.

Distilled test case:
data:text/html,<p>a</p><p>b</p><p>c</p><p>d</p><p>e</p><p>f</p><p>g</p><p>h</p><p>i</p><div role="application"><dialog id="dialog">hi<button>ok</button></dialog></div><script>setTimeout(() => dialog.showModal(), 50);</script>

Based on James's comments, closing this as won't fix, unfortunately.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.