WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Return to Top Link

for

From: Isabel Holdsworth
Date: Oct 22, 2018 2:09AM

Hi JP,

As well as scrolling the page, does the <main> tag receive focus? If
so IMHO its tabindex should be set to -1, otherwise keyboard users
without a screenreader will encounter a strange focus order. If
screenreaders aren't working correctly with this set-up, then they are
buggy. This is how our dialogues work, and we don't seem to have any
problems with them. When the dialogue opens up, the container, which
has a tabindex of -1, receives focus. Then when the user tabs again,
the first focusable element within the container receives focus. It
seems to work fine.

Cheers, Isabel

On 19/10/2018, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> That sounds like a Jaws bug to me.
>
> I believe this may happen with NVDA and Firefox as well in some situations
> -- a bug is listed below
>
> https://github.com/nvaccess/nvda/issues/7897
>
> Jonathan
>
> Jonathan Avila, CPWA
> Chief Accessibility Officer
> Level Access
> <EMAIL REMOVED>
> 703.637.8957 office
>
> Visit us online:
> Website | Twitter | Facebook | LinkedIn | Blog
>
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination, distribution
> or copying of this communication is strictly prohibited.
>
>