Closed Bug 1375918 Opened 7 years ago Closed 7 years ago

Re-check touchscreen / a11y severance code for Windows 10 Creators Update

Categories

(Core :: Disability Access APIs, enhancement)

Product:
Core
Component:
Disability Access APIs
Platform:
Unspecified
Windows 10
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

(Whiteboard: aes+) 

I've been hearing a lot of reports lately about Windows 10 touchscreen users getting a11y again. I think we should take another look at this, specifically focusing on Creators Update.
Emanuel, you mentioned in bug 1375412 that you're still having to force-disable a11y. Are you running Windows 10 Creators Update? Do you have a touchscreen?
Flags: needinfo?(emanuel.hoogeveen)
Hi Aaron, my profile is pretty old and that setting is probably vestigial. I cleared out some of my weird custom settings yesterday, and I still get e10s as expected (though e10sMulti is blocked by my add-ons).

I'm running Windows 10 with the Creators Update, and I don't have a touchscreen. How can I tell if a11y is enabled? The value of accessibility.lastLoadDate seems to be updated every time I open Firefox.
Flags: needinfo?(emanuel.hoogeveen)
Note: for anyone using windows 10 unintentionally instantiating accessibility, please look at about:telemetry, "Scalars" and see if there is an accessibility instantiator listed, and report it here.
Resolving for now, I think it's non-touchscreen external instantiators that we're seeing.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.