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

Bryan Garaventa wrote:

“This implies two functions for false, which seems to state that false
should be conveyed as ‘not current’ as well as ignored by user agents at the
same time. Since the value of false should be different from undefined, the
following is clearer:

 

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

 

I think that’s how it was in earlier drafts. The concern was that it could
lead to ATs announcing items other than the current one, leading to a lot of
extra verbosity.

 

Léonie.

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup