WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bypass Blocks for Keyboard users

for

From: Birkir R. Gunnarsson
Date: Jul 15, 2015 11:41AM

I would make the lack of a skip link as a strong recommendation under
WCAG SC 2.4.1.
I would describe it along the lines of:
"Though implementing a heading and landmark structure is technically
sufficient to meet this success criterion, and it does for users of
assistive technology apps such as screen readers, the lack of browser
support for keyboard navigation to landmarks creats a major usability
issue for people who rely on keyboard only or keyboard simulators).
for possible additional background or remediation suggestions I would
normally point them to
http://terrillthompson.com/blog/161
(except there is no need for the JQuery backup solution, it is
sufficient to put tabindex="-1" on target).
anticipating a large user base with outdated browsers and assistive
technologies).
I have never seen anyone actually implementing the skip to widget
developed by PayPal
https://github.com/paypal/skipto
but it is an interesting aproach.
I cannot call this as a violation of any other WCAG SC, 2.1.1 only
states that all functionality on page is operable via keyboard only,
2.2.2 requires no keyboard traps.
There is nothing about excessive tabbing in WCAG SC except for 2.4.1.
They could post links to browser add-ons that enable keyboard
navigation to landmarks, but that is probably not the greatest
solution.
Going forward We, as a community, need to keep pushing on browser
vendors to do their bit and implement some sort of keyboard shortcuts
to landmarks, at least to the main landmark.
Thank




On 7/15/15, Joseph Sherman < <EMAIL REMOVED> > wrote:
> Let me ask another way. A webpage has a left navigation menu of 20 items, or
> top navigation of 5 items. A keyboard-only user has to tab through these on
> every page within the site, but the main content has a landmark or h1 tag.
> Technically this seems to meet 2.4.1, but would seem to violate the spirit
> of the guideline until browsers can use landmarks. Do I give the site a pass
> for 2.4.1, but note the usability issue? If the developer is required to
> meet WCAG 2.0 and this is a pass, is there another guideline I can use to
> get them to add a skip link?
>
> Thanks.
>
> Joseph
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: Tuesday, July 14, 2015 4:57 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Bypass Blocks for Keyboard users
>
> The idea behind landmarks was (and is) the hope that browser vendors will
> take advantage of them, and implement shortcut mechanisms for keyboard only
> users.
> As for 2.4.1 as it related to keyboard only users, I usually look more at
> accessible mega menus, accordions, tabs/tabpnels and other complex widgets
> that reduce the amount of key presses necessary to get to the desired
> content on a web page.
>
> E.g. if your site boasts a navigation megamenu that consists of 4 or 5 main
> menu links, each with 8 to 10 item submenus, it is important to enable
> keyboard navigation pattern that enables the user to utilize the arrow keys
> to quickly navigate within the menu rather than only implementing shortcuts
> for mouse users but leave the keyboard only user to fend for him or herself,
> armed with nothing but the tabkey.
>
>
>
> On 7/14/15, Joseph Sherman < <EMAIL REMOVED> > wrote:
>> The second group of Sufficient Techniques for 2.4.1 - Bypass Blocks
>> involves grouping blocks of repeated material with ARIA, headings,
>> frames, etc. None of these techniques seem to help
>> keyboard-only/magnification users, who still may have to move through
>> a bunch of navigation links. Am I missing something here?
>>
>> Joseph
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.