Opened 11 years ago

Closed 11 years ago

#5702 closed defect (fixed)

review dijit templates for proper use of waiRole=presentation

Reported by: Becky Gibson Owned by: Becky Gibson
Priority: high Milestone: 1.2
Component: Accessibility Version: 1.0
Keywords: a11y FF3 Cc: simonjb
Blocked By: Blocking:

Description (last modified by Becky Gibson)

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.

Change History (6)

comment:1 Changed 11 years ago by simonjb

(In [12413]) Added role="presentation" to the templates for Button, ComboButton?, and DropDownButton?; refs #5702

comment:2 Changed 11 years ago by guest

The latest tree example also needs work with regards to role="presentation".

comment:3 Changed 11 years ago by Becky Gibson

(In [12709]) refs #5702 added waiRole=presentation on tree rowNode.

comment:4 Changed 11 years ago by Becky Gibson

(In [12717]) refs #5702 updated tooltipDialog template to include waiRole=Presentaton on divs which do not belong in the a11y hierarchy

comment:5 Changed 11 years ago by Becky Gibson

Milestone: 1.11.2

I think most have been fixed but leaving open for 1.2 so can double check.

comment:6 Changed 11 years ago by Becky Gibson

Description: modified (diff)
Resolution: fixed
Status: newclosed

I believe most instances are fixed so am closing. Will open individual tickets if more instances are discovered.

Note: See TracTickets for help on using tickets.