WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Return to Top Link

for

From: Jonathan Avila
Date: Oct 17, 2018 5:28PM

Hi, the problem that I've seen with some browsers like Firefox is that when certain tabindex values are set on a container and the user presses H to move to a heading and then presses tab the screen reader sometimes doesn't move to the next focusable control after the heading because the tabindex on the container seems to throw it off.

Jonathan


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Wednesday, October 17, 2018 2:39 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Return to Top Link

What is the problem with JAWS and IE with the tabindex="-1"?

IE actually requires you to have tabindex="-1" on any element that might receive focus or if that element is used in an aria-labelledby. Without tabindex="-1", while the page might scroll to that element when focus is sent to it (via javascript), if you tab after the page scrolls, the focus wasn't really moved to that element and the tab focus goes to whatever was after where the focus was previously.

This is documented on microsoft -
https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/accessibility/gg701963(v=vs.85)#accessible-html-elements

So I'm puzzled what problem you're seeing when using tabindex="-1"

Glen

On Wed, Oct 17, 2018 at 8:31 AM JP Jamous < <EMAIL REMOVED> > wrote:

>
> <main id="page-content" tabindex="-1">
>
> I don't like the tabindex="-1" because JAWS in IE causes problems when
> tabbing.
>
>