WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Return to Top Link

for

From: JP Jamous
Date: Oct 17, 2018 10:49AM

That was exactly what I suggested to the developer. I would like to set the
focus on the H1, but the 34 other web sites that this component is a part of
do not all have a H1 after main. It is an ugly situation.



--------------------
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 10:55 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Return to Top Link

> <main id="page-content" tabindex="-1">

Perhaps setting focus to the heading directly below the beginning of the
main element would be better than moving to the main element itself to avoid
any issues with tabbing issues that may result from tabbing after quick key
navigation with screen readers. Some browsers may also require calling the
focus method on the element as well.

Jonathan

Jonathan Avila
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 [mailto: <EMAIL REMOVED> ] On Behalf
Of JP Jamous
Sent: Wednesday, October 17, 2018 10:31 AM
To: 'WebAIM Discussion List'
Subject: [WebAIM] Return to Top Link

Folks,



Another interesting situation I have on my plate. There is a "Return to Top"
link that is supposed to jump the user to the page content or <main>. It
uses a Jquery to perform a page scroll.



I tested the link and sometimes it works and other times it fails. When it
fails, it jumps the screen reader user to the top of the DOM. The other
concern is that <main> has this markup.



<main id="page-content" tabindex="-1">



I don't like the tabindex="-1" because JAWS in IE causes problems when
tabbing.



Any idea what would be the best way to implement this so it is always
functional and does not malfunction at times? Any feedback will be greatly
appreciated.







--------------------

JP Jamous

Senior Digital Accessibility Engineer

<mailto: <EMAIL REMOVED> > E-Mail Me | <http://linkedin.com/in/JPJamous>; Join
My LinkedIn Network

--------------------





http://webaim.org/discussion/archives
http://webaim.org/discussion/archives