Closed
Bug 1895408
Opened 2 years ago
Closed 2 years ago
Expose meter "value region" via AXValueDescription on macOS
Categories
(Core :: Disability Access APIs, defect, P2)
Tracking
()
RESOLVED
FIXED
128 Branch
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: morgan, Assigned: morgan)
References
Details
Attachments
(1 file)
The HTML spec defines a value region for meter (optimal, sub-optimal, or "even less good", which we should probably take WebKit's "critical" wording on) depending on the low, high, and optimum DOM attributes. We should expose this via AXValueDescription to match Safari's current behaviour. Note that this may change to AXLevelIndicator in the future per https://github.com/w3c/html-aam/issues/536
|
Assignee | |
Updated•2 years ago
|
OS: Unspecified → macOS
Hardware: Unspecified → Desktop
Summary: Expose meter → Expose meter "value region" via AXValueDescription on macOS
|
|
Assignee | |
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
|
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → mreschenberg
Status: NEW → ASSIGNED
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3c922f0d2d03
Add support for exposing critical, supoptimal, optimal meter values via AXValueDescription r=Jamie
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•