Ticket #5702 (closed defect: fixed)
review dijit templates for proper use of waiRole=presentation
| Reported by: | becky | Owned by: | becky |
|---|---|---|---|
| Priority: | high | Milestone: | 1.2 |
| Component: | Accessibility | Version: | 1.0 |
| Severity: | normal | Keywords: | a11y FF3 |
| Cc: | simonjb |
Description (last modified by becky) (diff)
Firefox 3 now puts divs into the accessibility hierarchy. Thus, any div that we use within a widget will need to have a role. Many elements will have a role for the widget type (tab, menu, tree, treeitem, etc) but any inner divs that are just for layout or structure will also need a role of presentation.
There have been several tickets filed for specific widgets, #5657, #5658, #5659, #5660, #5661, this is for the remaining ones.
From the FF a11y dev:
Right, in FF2 the divs were not exposed unless they had a role. Now they are always exposed, because as it turns out they're important to screen readers in regular document content because it indicates where blank lines exist. But inside of a widget like a tab or button they are extra clutter in the a11y hierarchy that could confuse a screen reader and should get role="presentation"
For tables, if you put *any* role on the <table> element that will remove all child table cell objects from the hierarchy, unless they themselves have a role attribute.
