Confirmed users
1,085
edits
Accessibility/TreeGrid: Difference between revisions
Jump to navigation
Jump to search
→Plan: - still rough
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) (→Plan: - still rough) |
||
| Line 32: | Line 32: | ||
* if tree grid, assume it expands relative to a row | * if tree grid, assume it expands relative to a row | ||
When should rows get an accessible name? | When should rows get an accessible name? | ||
* if it has title, aria-label, aria-labelledby ? | |||
* if none of above, when should we do name from children (cells)? | |||
* possible heuristic: if <table> has no role... don't mess with it too much. | |||
* for xul treegrids: role is tree... we have row objects which become treeitem or outline item, and the outline item will get cell children. check with orca for bustage. | |||
* for aria: use treegrid if actual structure of the grid is being influences... if expanded content is assoc with rows use treegrid, if expanded content is assoc with cells, use grid. we need to support row and col objects. | |||
Row/TreeItem name synthesis should occur when: (not sure which of these get name synthesis and which do not) | |||
* always | |||
* when the row is focusable | |||
* xul only | |||
* xul plus aria | |||
* xul plus aria treegrid only (but not grid) | |||
States, Relations, Events? | |||
* the events and states depend on hints. if a cell has an expanded button, you need to put expanded on that button... use aria-controls. | |||
* if cell controls row expansions use aria-controls. | |||
Aaron was saying this at CSUN: | |||
* should we be more conservative with ARIA/HTML should we be putting the concatenated name on the row? do we do it for aria.. | |||
* for rows in aria should we do it fresh and new... not worry about concat names. | |||
* if a row is focusable, then expose it (create an accessible object). | |||