Confirmed users
1,085
edits
Accessibility/TreeGrid: Difference between revisions
Jump to navigation
Jump to search
→Plan
DavidBolter (talk | contribs) (→Plan: - still rough) |
DavidBolter (talk | contribs) (→Plan) |
||
| Line 17: | Line 17: | ||
= Plan = | = Plan = | ||
When should rows get an accessible name? | When should rows get an accessible name? | ||
| Line 49: | Line 35: | ||
* 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. | * 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. | * if cell controls row expansions use aria-controls. | ||
* if a cell has aria-expanded then: | |||
** if grid, assume it expands the cell | |||
** if tree grid, assume it expands relative to a row? | |||
Aaron was | Aaron was wondering 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.. | * 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. | * 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). | * if a row is focusable, then expose it (create an accessible object). | ||