Open Bug 1949921 Opened 23 days ago Updated 20 days ago

Windows Narrator does not automatically start reading document contents

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Windows 11
defect

Tracking

()

Tracking Status
firefox137 --- affected

People

(Reporter: nlapre, Unassigned)

References

(Blocks 1 open bug)

Details

STR:

  1. Turn on UIA support in about:config; set accessibility.uia.enable to true.
  2. Launch Windows Narrator.
  3. Type or paste data:text/html,hello world into the Awesomebar, then press Enter.

Expected: Narrator reads the text in the document without any keyboard input, as it does in Edge. The specific utterance is: "loading complete, scan, document, hello world"
Actual: The user must enter a keyboard command (such as Narrator + Down Arrow) to get Narrator to start reading. The specific utterance is: "scan"

The word "scan" comes from switching into scan mode (it would have been off while in the Awesomebar). Firefox is missing loading notifications and the "document" announcement, but those aren't the purpose of this bug. This bug specifically deals with the lack of automatic reading of the content.

It's not clear to me that we want this behavior, but putting myself in the shoes of most users, I think it's a potentially desirable default.

I wonder whether this is because we don't fire UIA_AsyncContentLoadedEventId. Chromium fires this at the same time it fires IA2_EVENT_DOCUMENT_LOAD_COMPLETE.

Firing UIA_AsyncContentLoadedEventId results in a "[page title] has finished loading" announcement, but it does not result in the page being read automatically. Hmmm.

This doesn't seem to work with the IA2 -> UIA proxy either (Gecko UIA disabled). So, it isn't a regression strictly speaking, though it'd obviously be good to fix, whether before or after we ship UIA.

(In reply to James Teh [:Jamie] from comment #2)

Firing UIA_AsyncContentLoadedEventId results in a "[page title] has finished loading" announcement, but it does not result in the page being read automatically. Hmmm.

And yet this Chromium commit has this to say:

This change fires UIA_AsyncContentLoaded as the UIA analogue to
IA2_EVENT_DOCUMENT_LOAD_COMPLETE. Narrator plans to use this to
determine when to start auto-reading webpages.

See Also: → 1950275
You need to log in before you can comment on or make changes to this bug.