WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Return to Top Link

for

From: JP Jamous
Date: Oct 18, 2018 6:12PM

Similar to what Jonathan mentioned. If the <main tabindex="-1"> and the user
is reading using down-arrow, once the user presses the tab key to set the
focus on the next link in the DOM, the <footer> obtains focus because other
footer links have tabindex="-1".

Once I had the developers remove tabindex="-1" from <main> JAWS was behaving
as it does in all browsers. So bottom line, JAWS in IE11 was selecting the
next tabindex="-1" or tabindex="0" and bypassing the whole list of links on
the page content.

That only happens in JAWS 2018 and IE11. I tested it with JAWS 2018 and
firefox and Chrome and the problem was not present. The tab selected the
link that is next in the DOM from where the cursor was last in the DOM.

That surely confuses a user because the user expects the next link in the
DOM after the position of the cursor to obtain focus. However, the user is
immediately jumped to the footer and has to either shift + tab to go back or
loop around the end of the DOM back to the top.



--------------------
JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network
--------------------


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

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.
>
>
http://webaim.org/discussion/archives
http://webaim.org/discussion/archives