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.
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Birkir R. Gunnarsson
> Sent: Friday, October 19, 2018 6:59 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Return to Top Link
>
> That sounds like a Jaws bug to me. I'd recommend filing it and having FS fix
> it.
> I think we can't always work around screen reader bugs, especially when the
> workaround may cause issues for other users (e.g. if removing the tabindex
> causes the skip link to break for keyboard only users, in this situation it
> might).
>
>
> On 10/18/18, JP Jamous < <EMAIL REMOVED> > wrote:
>> 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-ex
>> plorer
>> /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.
>>>
>>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > http://webaim.org/discussion/archives
> > > > > >