Closed
Bug 1657505
Opened 4 years ago
Closed 4 years ago
Add AXFrameSearchKey to search class for VO support
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
RESOLVED
FIXED
83 Branch
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: morgan, Assigned: morgan)
References
Details
Attachments
(1 file, 1 obsolete file)
I'm not sure if this gets surfaced in the voiceover menu itself (hard to tell if this maps to "web spots", but that'd be my guess).
This is one of the keys VO requests on pageload, though, so its high priority to implement.
I can't understand Safari's search infrastructure, but Chrome seems to classify accessibles with role AX_WEB_AREA and AX_WEB_AREA_ROOT to this search key. I don't know if we have an equivalent to the latter, but the former is just roles::DOCUMENT, which I'll add a patch for now :)
I'm wondering if there's a distinction here between TLDs and iframes, chrome's code doesn't make me think so but 🤷♀️
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P1
Updated•4 years ago
|
Attachment #9168315 -
Attachment is obsolete: true
Assignee | ||
Comment 2•4 years ago
|
||
Pushed by mreschenberg@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/229a1d3fde95 Add support for AXFrameSearchKey to VO rotor r=eeejay
Comment 4•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•