As of v0.22.2 TagMultiselectWidget inherits role=listbox of DraggableGroupElement.
This doesn't seem to make lot of sense in context of TagMultiselectWidget and also leads to accessibility error because listbox [[ https://www.w3.org/TR/wai-aria/roles#listbox | requires owned role=option items ]].
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| DraggableGroupElement: Remove ARIA roles & attributes | oojs/ui | master | +0 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T119044 TagMultiselectWidget (earlier CapsuleMultiselectWidget): UX and functionality improvements | |||
| Open | None | T158400 Streamline & improve tag component TagMultiselectWidget (former CapsuleMultiselectWidget) | |||
| Duplicate | None | T162965 Clarify & streamline user experience of TagMultiselectWidget variants | |||
| Resolved | Volker_E | T170267 TagMultiselectWidget (draggable) shouldn't inherit `role=listbox` of DraggableGroupElement |
Event Timeline
We should probably move the attribute from DraggableGroupElement initialization to DraggableGroupWidget as it could also hurt screen readers in possible other combinations.
Change 364453 had a related patch set uploaded (by VolkerE; owner: VolkerE):
[oojs/ui@master] DraggableGroupElement: Move ARIA role to DraggableGroupWidget
It seems most appropriate to have a draggable with role=list and elements with listitem.
I'm not convinced DraggableGroupElement and DraggableElement should be setting any roles. The classes that these are mixed into should probably be doing that.
@matmarex Yes, I was more referring to a concept like DraggableGroupWidget in the demo than any role on those mixins.
Change 364453 merged by jenkins-bot:
[oojs/ui@master] DraggableGroupElement: Remove ARIA roles & attributes