E-mail List Archives
WebAIM-Forum Digest, Vol 124, Issue 14
From: Gus Reiber
Date: Jul 28, 2015 3:27PM
- Next message: Guy Hickling: "Re: Screen Readers as a Development Tool for Web Developers"
- Previous message: Moore,Michael (HHSC): "Re: Screen Readers as a Development Tool for Web Developers"
- Next message in Thread: None
- Previous message in Thread: None
- View all messages in this Thread
Hi Asa,
Thanks for your quick response, and I apologize for my slow response.
Any chance you can pass along a direct email?
We would very much like to get Jenkins 508 compliant.
Gus
greiber_at_cloudbees_dot_com
On Thu, Jul 16, 2015 at 11:00 AM, < <EMAIL REMOVED> >
wrote:
> Send WebAIM-Forum mailing list submissions to
> <EMAIL REMOVED>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> <EMAIL REMOVED>
>
> You can reach the person managing the list at
> <EMAIL REMOVED>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
>
> Today's Topics:
>
> 1. Re: Bypass Blocks for Keyboard users (Steve Sawczyn)
> 2. Re: Bypass Blocks for Keyboard users (Birkir R. Gunnarsson)
> 3. Downloadable API server for Wave (Gus Reiber)
> 4. Re: Downloadable API server for Wave (Asa Baylus)
> 5. Accessibility Camp Sydney July 22 (Jennison Mark Asuncion)
> 6. Free Microsoft Ebooks (Jim Allan)
>
>
> ---------- Forwarded message ----------
> From: Steve Sawczyn < <EMAIL REMOVED> >
> To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
> Cc:
> Date: Wed, 15 Jul 2015 13:28:28 -0500
> Subject: Re: [WebAIM] Bypass Blocks for Keyboard users
> 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: Guy Hickling: "Re: Screen Readers as a Development Tool for Web Developers"
- Previous message: Moore,Michael (HHSC): "Re: Screen Readers as a Development Tool for Web Developers"
- Next message in Thread: None
- Previous message in Thread: None
- View all messages in this Thread