WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: In-page links and programmatic focus

for

From: Jim Homme
Date: Sep 12, 2016 2:48PM

Hi,
Where can JavaScript be found that shows this technique?

Thanks.

Jim


=========Jim Homme,
Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
<EMAIL REMOVED>
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
Sent: Monday, September 12, 2016 4:43 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] In-page links and programmatic focus

Some of these bugs still persist, especially on pages such as single page apps or those that include significant client side scripting, largely because the use of an id hash changes the page url and acts almost like a page refresh in some cases. I saw this recently with a modal that included same page links within it.

The use of the JavaScript focus() method is still the most reliable method for doing this reliably across all browsers, plus a return false in the script to prevent any automatic submission relating to the clicking of native links that may inadvertently refresh the page.

The addition of tabindex="-1" on any targeted static element is still needed to ensure that Tab can be pressed from that location to proceed to the next active element in the tab order, otherwise the visual focus may scroll but keyboard functionality will still be impaired.

Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
<EMAIL REMOVED>
415.624.2709 (o)
www.SSBBartGroup.com

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jared Smith
Sent: Monday, September 12, 2016 1:11 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] In-page links and programmatic focus

Paul Adam wrote:
>
> If the in page link goes to a focusable element like with tabindex=-1
> then keyboard focus will shift to that element properly.

This was not the case for a long time with Chrome and Safari (and IE under some conditions) - thus many people used JavaScript to set focus. I believe these bugs have been fixed within the last year or so.

Jared