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

My sense from the discussion is that aria-currentfor is not worth pursuing,
so I’ll park it for now. If anyone has good reasons for us to pick it up
again, let me know.

 

I’ve updated the aria-current definition based on suggestions from this
discussion. It no longer requires a navigation container in its ancestry,
and can now be applied to all elements in the base markup. I’ve also amended
the wording of the recommended UA behaviour for false/undefined, and
referenced its relationship to visual styling.

 

As always, comments welcome…

 

1.       Aria-current attribute.

 

Indicates the element that represents the current item within a container.

 

The aria-current attribute indicates whether the element is current (true),
or not current (false). If the aria-current attribute is false or undefined,
the current state of the element should not be conveyed by User Agents.

 

For example the aria-current attribute may be used to indicate the current
document in a collection or the current step in a process, where the current
item is otherwise highlighted visually.

 

Note

The aria-current attribute is similar to the aria-selected attribute, but
there are important differences. the aria-selected attribute indicates the
selected state of children within certain widgets, whilst the aria-current
attribute indicates the current element within the scope of a container.

 

Characteristics of aria-current

Used in roles: All elements of the base markup.

Value: true/false/undefined

 

Values of aria-current

true: The element is current

false: The element is not current

undefined: The element cannot be current

 

 

 

Léonie.

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup