[WG: Accessibility] Agenda for Today's Sakai Accessibility Working Group Teleconference

[Richwine, Brian L]

Agenda:

·         Accessibility Review Update

o   Accessibility Review QA server Status: (http://sakaicle1-trunk.uits.indiana.edu:8181/portal)

§  Currently on Sakai 2.9.0 - Alpha 02.

§  Will most likely upgrade the AR-QA server with Sakai 2.9.0 - Alpha 03 this weekend.

§  First Sakai 2.9.0 Beta Release is scheduled for December 16th

o   Accessibility Review Status

§  So far 11 tools have Accessibility testing coverage with 30 Resulting Testing result pages

·         Results posted at: https://confluence.sakaiproject.org/display/2ACC/Sakai+2.9+Accessibility+Review+Results

·         Tools with some review coverage so far include:

o   Admin tools:

§  Become a User

§  Sites

§  Users

§  Worksite Setup

o   Gateway tools:

§  About

§  Acknowledgements

§  Features

§  New Account

§  Site Browser

§  Training

§  Welcome

o   Main Tools:

§  Announcements

§  Assignments

§  Preferences

§  Neoportal

§  Profile2

§  Worksite Setup

o   Accessibility Timeline

§  Will be going through existing review results this weekend and evaluating priority of issues

§  Will be identifying existing Jira's for issues (and updating them as needed to reflect versions affected and assignments) and creating new Jiras as needed next week (12/5-12/15)

§  Promised to have Jira's cut from the issues found in the Accessibility Review by 12/15

o   Current Efforts

§  Brian is focusing on Neoportal accessibility issues, hopefully SAK-20916 (Accessing a Site from NeoPortal Worksite Navigation Causes Internet Explorer 8 and 9 to Crash when Used with the JAWS Screen-Reading Software) will be in Sakai 2.9.0-A03 so Mary can do more testing of the Neoportal without IE/JAWS crashing.

§  Brian is looking at the action bar ARIA markup this weekend to provide a recommendation on what Is best to work in JAWS and VO and also not lead to crashing.

§  Brian is writing a new jQuery based menu for the "Add" and "Action" menus from scratch instead of using the jQueryUI menu widget - much lighter, cleaner, code using existing CSS and only one js file. Will have the same look and feel for mouse users as the existing menus. Will have Mary test it with JAWS next week.

§  Joe and Mary working through Instructor personas of Assignments and Gradebook

o   Concerns

§  IE and FF are frequently crashing when being used in combination with JAWS 12. Crashing frequently on Sakai CLE and even more frequently with Sakai OAE.

§  Mary is hearing reports that JAWS 13 has many stability issues as well. A supposedly more stable version of JAWS 13 will be released next week and hopefully we can do some testing with it to see how it performs.

·         Jiras:

o   https://jira.sakaiproject.org/browse/SAK-20631 - Resource Tool "Add" and "Action" menus difficult for screen-reader users to navigate and operate.

§  Turns out jQueryUI menu widget is not in current jQueryUI releases. jQueryUI menu depends on several CSS and JS files.

§  The jquery.ui.menu.js found in the current release of jQueryUI 1.9pre is quite a bit different than what Kiran started with. Has a dependency of jQuery 1.6.3+ (not currently found in Sakai 2.9)

§  Have started writing a much simpler (one file) jQuery based script that uses existing CSS and jQuery libraries in Sakai CLE and has the same look and feel as the existing menus for mouse users while having ARIA and keyboard access for others.

§  Concerned that the standard ARIA menu operation is different than the top navigation menus found in the NeoPortal. Will try to blend both keyboard interactions if possible.

o   https://jira.sakaiproject.org/browse/SAK-21507 - The three skip navigation links do not work in Safari or Chrome, https://jira.sakaiproject.org/browse/SAK-21502 - Skip Navigation links aren't visible to allow access to sighted keyboard only users, and https://jira.sakaiproject.org/browse/SAK-19559 - "Jump to Worksite List" Skip Navigation Link Present on Login Page

§  Sent an email to the list regarding these three Jiras on November 29 asking for input on a suggested fix

§  Testing with Mary shows they work in IE and FF on windows plus have unexpected usability improvements in how the skip navigation works with Firefox.

§  Concerned over global changes to the CSS ruleset for the .skip selector

·         Concern is over the testing required to prove global change doesn't cause unwanted problems.

·         Changes to the .skip ruleset change it from moving text off-screen (left:-999px, top:-999px) to simply masking out the content (height:1px, width:1px, overflow:hidden)

·         This offers benefits that it allows elements marked up as such to receive keyboard focus in Firefox, Safari, and Chrome

·         Fixes problem where focus indication (the dotted outline) would flow off the element and off the screen in an attempt by the browser to place the outline around the off-screen content.

§  Also seeking feedback on changes to the skip nav links themselves

·         Suggesting addition of an onclick handler with javascript to move the focus directly since many browsers don't actually move the focus when a same page link is activated (FF, Safari, Chrome, Opera)

·         Suggested onclick handler gracefully falls back to the default link action if the call to focus fails or javascript is disabled

§  Also requires changes to the same page link target as webkit browsers (Safari, Chrome) will not give focus to empty elements (named anchors are empty elements).

·         Suggested fix's onclick handler on the skip nav links targets the hidden "Worksites list begins here", "Tools List begins here", and "Content begins here" headings instead of the named anchors.

·         Leaves the link's href target to the named anchors

§  Changes to the "#skipNav a" css ruleset in portal.css make the skip navigation links usable to sighted keyboard only users.

·         Modified CSS with addition of :focus and :active pseudo classes to override the .skip css rules and bring the links into view when they get focus (:active is required for older IE browsers).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20111201/a4cdfbae/attachment-0001.html