WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: announce aria-current before content of element

for

From: glen walker
Date: Nov 6, 2018 11:05AM

A screen reader will announce an element's name, role, value, and state,
not particularly in that order nor may all four items apply. The order is
up to the assistive technology and the order can change depending on how
you navigate to the element (tab navigation vs arrow keys). All that's
important is that you use the proper semantic markup. The user will be
used to a certain order because they are most likely very familiar with the
AT they are using. If you try to force a different order, it might sound
odd to them.

All you really have control of is the accessible name of the element. If
you really, really, need something read in a certain order, then you'll
need to put that text into the accessible name (which I am not
encouraging). In your case, it means not using aria-current but instead
putting the "current" into the accessible name and probably visually hiding
it.

<span class="self-link"> <span class="sr-only">current page </span>
something </span>


On Tue, Nov 6, 2018 at 9:34 AM Zsolt Edelényi < <EMAIL REMOVED> > wrote:

> Hi all,
>
> I have this HTML:
>
> <span class="self-link" aria-current="page">something</span>
>
> JAWS (2018 +Win10 +Firefox ) says: "something current page". Current
> page *announced **after *the content of the span element.
>
> I have an another HTML:
>
> <a href="#" aria-current="page">something</a>
>
> read as "current page something link". Current page is *announced before
> *the content of the anchor element.
>
>
> Do you know to achieve that JAWS would read the "current" *always before
> the content *of the html element?
>
>
> Thank you.
>
> --
> Zsolt Edelényi
> <EMAIL REMOVED>
>
> > > > >