WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader behaviour > tabindex=-1

for

From: Birkir R. Gunnarsson
Date: Dec 15, 2017 5:14AM

Hi
In example 1, the div has an accessible name which is the text of the
heading (because of aria-labelledby).
A screen reader will read the accessible name of the element that is
focused. It would not read the rest of the text inside that div, not
unless you tagged the div as a dialog and used aria-describedby to
point to the container for the rest of the text (I generally advise
against that anyway, since too much automated screen reader announcing
is not good for users(.
Your second example <div> has no accessible name, so a screen reader
should not automatically read anything when it receives focus.
A screen reader vendor may choose to read the first line of text
inside it, just as some content, but that is up to individual screen
reader vendors to determine, there is nothing in the spec that
dictates what should happen.



On 12/15/17, Fernand van Olphen < <EMAIL REMOVED> > wrote:
> Hi everyone,
>
> I have a question about screen reader behaviour.
>
> Below are two examples of <div's> that are programmatically focusable.
>
> Example 1:
>
> <div role="region" aria-labelledby="heading" tabindex="-1">
> <h1 id="heading">Heading </h1>
> </div>
>
> Example 2:
>
> <div tabindex="-1">
> <h1> Heading</h1>
> </div>
>
>
> The first example uses aria-labelledby.
> The second example doesn't.
>
> My question:
> In example 1 a screen reader will automatically start reading the heading,
> once the <div> is focused,
> In example 2, once the <div> is focused, will a screen reader automatically
> start reading what's inside the div?
>
>
>
> Regards,
>
> Fernand van Olphen
> Accessibility Advisor
> Municipality of The Hague,
> www.denhaag.nl
>
>
>
> De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:
> http://www.denhaag.nl/disclaimer
> > > > >


--
Work hard. Have fun. Make history.