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

Alexander Surkov wrote:

“Do I understand that typical scenario of this attribute looks the following way:

<div id="nav">

  <button aria-current="false" aria-currentfor="nav">1</button>
  <button aria-current="true" aria-currentfor="nav">2</button>
  <button aria-current="undefined">3</button>

</div>

If so then aria-current="undefined" dupes aria-currentfor, or do you consider the scenario when UA fixes missed aria-currentfor?”

 

Good question. My understanding is that aria-currentfor would only be needed on the element with aria-current – to setup the scope for the currently indicated item.

 

So in your example buttons 1 and 3 would not have their state indicated, but button 2 would be identified as the current item within the scoping container/div.

 

 

Léonie.

 

 

-- 

Senior Accessibility Engineer, TPG

@LeonieWatson @PacielloGroup