E-mail List Archives
Re: Bypass Blocks for Keyboard users
From: Birkir R. Gunnarsson
Date: Jul 15, 2015 12:43PM
- Next message: Gus Reiber: "Downloadable API server for Wave"
- Previous message: Steve Sawczyn: "Re: Bypass Blocks for Keyboard users"
- Next message in Thread: Guy Hickling: "Re: Reply for the thread: Bypass Blocks for Keyboard users"
- Previous message in Thread: Steve Sawczyn: "Re: Bypass Blocks for Keyboard users"
- View all messages in this Thread
Oh don´t get me wrong.
I would cite with Steve in a heartbeat if push came to a shove.
Fortunately the recommendation alone, with a practical demo if
necessary, is usually enough to make developers see the light, hear
the sound, smell the stink .. whatever you want to call it.
On 7/15/15, Steve Sawczyn < <EMAIL REMOVED> > wrote:
> I realize this is very controversial, but I still lean toward calling a
> 2.4.1 violation if a skip link isn't present. My reasoning is that while
> the techniques don't specifically address keyboard users, I feel it's not in
> the spirit of WCAG to call for a mechanism that can't be used by the user
> base most highly impacted. Sure browsers could and should add keyboard
> support for landmark/heading navigation, but until that's a reality, we have
> real users with real barriers with no real solution other than to say that
> the "mechanism" actually should be considered to be functionality and hence
> available to keyboard users.
>
> Steve
>
>
>
- Next message: Gus Reiber: "Downloadable API server for Wave"
- Previous message: Steve Sawczyn: "Re: Bypass Blocks for Keyboard users"
- Next message in Thread: Guy Hickling: "Re: Reply for the thread: Bypass Blocks for Keyboard users"
- Previous message in Thread: Steve Sawczyn: "Re: Bypass Blocks for Keyboard users"
- View all messages in this Thread