This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24984 - Degree of detail and best way to present for AX state and action mappings
Summary: Degree of detail and best way to present for AX state and action mappings
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jason Kiss
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2014-03-09 21:09 UTC by Jason Kiss
Modified: 2014-03-12 09:56 UTC (History)
6 users (show)

See Also:

Attachments

Description Jason Kiss 2014-03-09 21:09:03 UTC 
The mappings for the other APIs indicate states and actions (and interfaces in some cases). For AX, we generally have just AXRole, AXSubrole, and AXRoleDescription, but in some cases, e.g., for the <a> element [1], we probably want to list additional AX attributes and/or actions, i.e. AXVisited and AXPress.

It would be good to agree on how detailed we want to get and come up with a convention for listing/presenting the AX attributes and actions.

[1] http://rawgithub.com/w3c/html-api-map/master/index.html#el-a