RE: ACTION-1442: Draft spec text for aria-current and aria-currentfor

Matt King wrote:

“Note: 
When applied to an element contained in a widget that supports selection,
the meaning of aria-current is different from the meaning of
[aria-selected]. Authors should not use aria-current in lieu of
aria-selected and should avoid using aria-current in circumstances where the
meaning of aria-current would be the same as aria-selected. For example, in
a single-select [tablist] where the selected [tab] element corresponds to
the displayed tabpanel, aria-current is unnecessary. However, if the
selected state of a tab is used to indicate which tab is selected for an
action, such as move, delete, or make current, then aria-current should be
used to indicate which tab represents the currently displayed tabpanel.”

 

This still feels a bit confusing. I’m tempted to suggest that aria-current
and aria-selected should never be used simultaneously on the same element.
The UX for someone hearing that an element was both selected and current
would be very confusing.

 

 

Léonie.

 

 

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup