Closed
Bug 1406657
Opened 8 years ago
Closed 1 year ago
Run beta experiment(s) disabling oop accessibility clients
Categories
(Core :: Disability Access APIs, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox58 | --- | affected |
People
(Reporter: jimm, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: inj+)
Once we have the ability to block a11y clients from accessing Firefox's accessible service, we want to run experiments on beta that selectively disable certain a11y clients based on certain criteria. The experiment would:
1) block a client or a set of clients for a period of hours or days or session.
2) once completed, the experiment would load a Mozilla web page for the user with a survey about the oop clients to see if the user was impacted negatively.
We'll use this data to determine if the clients being tested should be added to a permanent blocklist.
Proposed selection criteria:
1) clients that access basic accessible information from the browser without navigating the accessible tree.
2) clients with questionable motivation
3) clients we want to nudge toward other extensibility methods (precursor to a permanent ban)
Updated•8 years ago
|
Priority: -- → P2
Updated•8 years ago
|
Updated•8 years ago
|
Priority: P2 → P3
Whiteboard: inj+
Updated•3 years ago
|
Severity: normal → S3
Comment 1•1 year ago
|
||
The original motivations for this are no longer as relevant, since Cache the World significantly improves a11y engine performance. While I'm not ruling this out completely, we have no plans to do this right now. If that changes, we can always reopen this or file a new bug.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•