Open Bug 1932843 Opened 11 days ago Updated 7 days ago

ATK: Expose text-input-type:search as object attribute for ARIA searchbox as well as for browser UI search fields (e.g. find in page)

Categories

(Core :: Disability Access APIs, enhancement)

Product:
Core
Component:
Disability Access APIs
Type:
enhancement

Tracking

()

People

(Reporter: jdiggs, Unassigned)

References

(Blocks 1 open bug)

Details

I discovered that according to the Core-AAM, on IAccessible2, the ARIA searchbox role has a mapping of Object Attribute: text-input-type:search". I like that mapping because it's consistent with the mapping of other text inputs as defined by the HTML-AAM. Plus it's always nice to have IA2 and ATK match when possible.

In addition, it would be super helpful if this mapping could be applied to browser UI search fields, such as the find-in-page and quick-search entries. (Right now Orca attempts to identify these heuristically, thus any change to the browser UI with respect to find risks breaking that identification.)

Jamie: Thoughts?

Hmm. Neither Firefox nor Chrome exposes IA2 text-input-type:search for role="searchbox". They do expose xml-roles:searchbox, though. So the spec doesn't match reality, which always leaves the question of which should be updated. :)

I follow your logic that it'd be nice to have <search> and role="searchbox" match. Given that neither browser follows the spec, the question is whether we should prefer text-input-type or xml-roles. A lot of ARIA roles map to xml-roles (for better or worse), so we pretty much get that for free for role="searchbox". But either way, we need to make a change here.

Blocks: aria
You need to log in before you can comment on or make changes to this bug.