E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 1 (In chronological order)

From: Gus Reiber
Date: Tue, Jul 28 2015 3:27PM
Subject: WebAIM-Forum Digest, Vol 124, Issue 14
No previous message | No next message

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 ADDRESS REMOVED = >
wrote:

> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS 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 ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS 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
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf Of Joseph Sherman
> Sent: Wednesday, July 15, 2015 9:00 AM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] Bypass Blocks for Keyboard users
>
> 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 ADDRESS 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 ADDRESS 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.
> > > at http://webaim.org/discussion/archives
> > > > > >
>
>
>
> ---------- Forwarded message ----------
> From: "Birkir R. Gunnarsson" < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Wed, 15 Jul 2015 14:43:04 -0400
> Subject: Re: [WebAIM] Bypass Blocks for Keyboard users
> 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 ADDRESS 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
> >
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf
> > Of Joseph Sherman
> > Sent: Wednesday, July 15, 2015 9:00 AM
> > To: 'WebAIM Discussion List'
> > Subject: Re: [WebAIM] Bypass Blocks for Keyboard users
> >
> > 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 ADDRESS 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 ADDRESS 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.
> > > > > archives at
> > http://webaim.org/discussion/archives
> > > > > > > > > > > >
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
>
>
>
> ---------- Forwarded message ----------
> From: Gus Reiber < = EMAIL ADDRESS REMOVED = >
> To: = EMAIL ADDRESS REMOVED = , Kohsuke Kawaguchi <
> = EMAIL ADDRESS REMOVED = >, Tracy Kennedy < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Wed, 15 Jul 2015 17:22:57 -0700
> Subject: [WebAIM] Downloadable API server for Wave
> Hello,
> I am an employee at CloudBees, one of the leading contributors to the
> Jenkins-ci.org community, and looking for help on 2 fronts.
>
> First, Jenkins is a build automation tool with a web GUI and as such, we
> would like to make that web GUI 508 compliant. The product is secured, so I
> am looking for a means of automatically crawling the pages of the
> application and am assuming this would preclude using the web based API.
> The "Downloadable API Manager (coming soon)" seems like what I want. Does
> anyone know an ETA for the coming soon aspect of the tool or know of a
> viable alternative?
>
> Second, since Jenkins is a build automation tool, we would be interested in
> adding an automation framework for 508 testing and HTML validation within
> Jenkins. Would this be something I could do with the Wave API Manager and
> does anyone out there have any experience automating 508 compliance
> testing?
>
> Thanks for your help,
> Gus
>
>
>
> ---------- Forwarded message ----------
> From: Asa Baylus < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc: Tracy Kennedy < = EMAIL ADDRESS REMOVED = >, Karl Groves <
> = EMAIL ADDRESS REMOVED = >, Kohsuke Kawaguchi < = EMAIL ADDRESS REMOVED = >
> Date: Wed, 15 Jul 2015 22:23:35 -0400
> Subject: Re: [WebAIM] Downloadable API server for Wave
>
> Hi Gus,
>
> You may not need to self host, you could create an SSH tunnel to support
> your testing using a hosted platform such as the Wave API behind the
> firewall.
> Here's an article with some helpful info:
> http://blog.trackets.com/2014/05/17/ssh-tunnel-local-and-remote-port-forwarding-explained-with-examples.html
> <
> http://blog.trackets.com/2014/05/17/ssh-tunnel-local-and-remote-port-forwarding-explained-with-examples.html
> >
>
> But a faster/easier solution is https://ngrok.com/ <https://ngrok.com/>
>
> In the open source space you have a number of good options which you can
> self host, Googles accessibility developer tools might be a good place to
> start.
> https://github.com/GoogleChrome/accessibility-developer-tools <
> https://github.com/GoogleChrome/accessibility-developer-tools>
>
> At Tenon.io some of our customers choose an SSH tunnel over an enterprise
> install. If you're set on self hosting though there are a number of
> options. Disclaimer, I'm the co-founder of http://tenon.io <
> http://tenon.io/>; and we are big Jenkins fans. Please feel free to
> contact me about how we can support Jenkins.
>
> Regards,
>
> Asa
>
> > On Jul 15, 2015, at 8:22 PM, Gus Reiber < = EMAIL ADDRESS REMOVED = > wrote:
> >
> > Hello,
> > I am an employee at CloudBees, one of the leading contributors to the
> > Jenkins-ci.org community, and looking for help on 2 fronts.
> >
> > First, Jenkins is a build automation tool with a web GUI and as such, we
> > would like to make that web GUI 508 compliant. The product is secured,
> so I
> > am looking for a means of automatically crawling the pages of the
> > application and am assuming this would preclude using the web based API.
> > The "Downloadable API Manager (coming soon)" seems like what I want. Does
> > anyone know an ETA for the coming soon aspect of the tool or know of a
> > viable alternative?
> >
> > Second, since Jenkins is a build automation tool, we would be interested
> in
> > adding an automation framework for 508 testing and HTML validation within
> > Jenkins. Would this be something I could do with the Wave API Manager and
> > does anyone out there have any experience automating 508 compliance
> testing?
> >
> > Thanks for your help,
> > Gus
> > > > > > > > >
>
>
>
> ---------- Forwarded message ----------
> From: Jennison Mark Asuncion < = EMAIL ADDRESS REMOVED = >
> To: webaim-forum < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Wed, 15 Jul 2015 21:38:23 -0700
> Subject: [WebAIM] Accessibility Camp Sydney July 22
> The first Accessibility Camp Sydney takes place on Wednesday July 22.
> Registration closes Friday July 17
> https://www.eventbrite.com.au/e/a11y-camp-sydney-tickets-17043938880
>
> Jennison
>
>
>
> ---------- Forwarded message ----------
> From: Jim Allan < = EMAIL ADDRESS REMOVED = >
> To: = EMAIL ADDRESS REMOVED = , = EMAIL ADDRESS REMOVED = , WebAIM Discussion List
> < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Thu, 16 Jul 2015 09:29:58 -0500
> Subject: [WebAIM] Free Microsoft Ebooks
>
> http://blogs.msdn.com/b/mssmallbiz/archive/2015/07/07/i-m-giving-away-millions-of-free-microsoft-ebooks-again-including-windows-10-windows-8-1-windows-8-windows-7-office-2013-office-365-sharepoint-2013-dynamics-crm-powershell-exchange-server-lync-2013-system-center-azure-clo.aspx
>
> --
> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan,
> Accessibility Coordinator
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>
>
> > > > >
>