Confirmed users
1,396
edits
Accessibility/TreeGrid: Difference between revisions
Jump to navigation
Jump to search
→Behaviour
m (→Behaviour) |
|||
| Line 40: | Line 40: | ||
* aria-level, aria-expanded - aren't used (general rules are applied) | * aria-level, aria-expanded - aren't used (general rules are applied) | ||
==== | ====Selection and Focus==== | ||
Cells can be focused/selected only. Rich insists on this because otherwise it is a pain to read cell content within heading information for screen readers users. But historically XUL trees allows rows or cells be selected. | |||
Focus is controlled by @tabindex attribute placed on cell element or by @aria-activedescedant attribute pointing to cell element if @tabindex is on grid element. | |||
Selection is controlled by aria-selected attribute placed on row or cell accessibles. If aria-selected="true" is placed on row accessible then it means all cell accessibles are selected also, i.e. aria-selected on the cell is taken into account if there is no aria-selected="true" on its row. Therefore widget author should rely on aria-selected attribute in order to change selection. IAccessibleTable interface methods used to modify selection (like selectRow and etc) operate with aria-selected attribute as well. Widget author should watch for aria-selected attribute changes if he needs to process selection changes from JS. There is a difference between pure ARIA grids and HTML tables so that current implementation of HTML tables uses DOM selection instead of aria-selected to implement selection methods of IAccessibleTable interface. However IAccessibleTable implementation of ARIA grids based on HTML tables uses DOM selection and aria-selected attributes together. | |||
====IAccessibleTable interface==== | ====IAccessibleTable interface==== | ||