Closed Bug 1956415 Opened 5 months ago Closed 5 months ago

Disable UIA when JAWS or NVDA are running

Categories

(Core :: Disability Access APIs, task)

task

Tracking

()

RESOLVED FIXED
138 Branch
Tracking Status
firefox138 --- fixed

People

(Reporter: Jamie, Assigned: Jamie)

References

(Blocks 4 open bugs)

Details

(Whiteboard: [uiaShipBlocker])

Attachments

(2 files)

I had hoped JAWS would just ignore Gecko's native UIA implementation. However, if Gecko native UIA is enabled, JAWS is all kinds of broken. We'll need to disable native UIA if JAWS is detected.

Initially, this just checks the accessibility.uia.enable pref.
Other checks will be added in subsequent patches.
All callers which previously checked the pref directly now call this function.

JAWS and NVDA will continue to use IA2 in Firefox.
However, enabling native UIA in Gecko causes them both to try to use UIA, which causes breakage.
The same is presumably true for other Vispero products, as they use components shared with JAWS.
Future versions of these products will handle this correctly themselves.
Until then, disable UIA when these products are detected.

As part of this, the UIA pref has been changed from a bool to a uint32_t.
This will cause existing configurations of this pref to be reset to the default, but this is okay because this pref has never been documented, exposed in the UI or intended for public usage.
This allows for three values: 0 to never enable, 1 to always enable and 2 to enable unless incompatible clients are detected.
This makes it possible for developers to test those clients with Gecko's UIA implementation when necessary.

Summary: Disable UIA when JAWS is running → Disable UIA when JAWS or NVDA are running
Blocks: 1956971
Blocks: 1956973
Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/75e9b40ec5d9 part 1: Add Compatibility::IsUiaEnabled. r=morgan https://hg.mozilla.org/integration/autoland/rev/d36718978096 part 2: Disable native UIA when JAWS, other Vispero products or NVDA are detected. r=morgan
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: