Opened 7 years ago
Closed 7 years ago
#17736 closed defect (invalid)
TabContainer and StackContainer: A WAI-ARIA widget must have an accessible name — at Version 1
Reported by: | shanshuo | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | tbd |
Component: | Dijit | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
I use dijit.layout.TabContainer? in a normal way like:
<div data-dojo-type="dijit.layout.TabContainer" style="width: 100%; height: 100%;"> <div data-dojo-type="dijit.layout.ContentPane" title="My first tab" data-dojo-props="selected:true"> Lorem ipsum and all around... </div> <div data-dojo-type="dijit.layout.ContentPane" title="My second tab" data-dojo-props="closable:true"> Lorem ipsum and all around - second... </div> </div>
And met the following error descriptions(for JAWS screen reader accessibility): "A WAI-ARIA widget must have an accessible name specified with aria-label, aria-labelledby or the widget's inner text".
I found that the TabContainer? outermost node has a role='tabpanel', but doesn't have a accessible name specified with aria-label, aria-labelledby or the widget's inner text.
According WAI-ARIA specification, TabContainer? should do so.
dijit.layout.StackContainer? has the same accessibility issue.
Change History (1)
comment:1 Changed 7 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The label must be specified by the application. It's impossible for the toolkit to specify the label because the toolkit cannot guess what the label is.