RE: Using aria-selected on focusable elements

Richard Schwerdtfeger wrote:

“I think the issue is that aria-selected is used in controls such that on
some platforms it becomes part of the selection model for a widget. I think
you are looking for something more global in nature.”

 

Yes. The reasons for not extending aria-selected make sense.

 

“It almost seems like you want something beyond "widget scope". Would this
also apply to breadcrumbs? We did not do a breadcrumb role in ARIA as we
thought it could be handled by existing widgets.”

 

I don’t think a breadcrumb role/widget is needed. More the ability to
indicate to AT users that the last step in a breadcrumb trail represents the
currently selected page.

 

<ul>

   <li><a href=”home.html”>Home</a>

   <ul>

      <li><a href=”about.html”>About</a>

      <ul>

         <li><a href=”meet.html” aria-current=”true”>Meet our team</a></li>

      </ul></li>

   </ul></li>

</ul>


“If you had this type of role how would you see a user interacting with it
differently from selection?”

 

>From the user’s perspective I’m not sure there would be any material
difference. They’d be made aware that the currently focused item was
selected/current/whatever. Whether that thing was a tab in a tabbed widget,
a page in a website, or a step in a process is a distinction beyond what
users would need/want to know.

 

 

Léonie.