[WG: Accessibility] Which QA server best reflects 2.9? Were accessibility issues filed and addressed?

[Humbert, Joseph A]

My answers are inline below.  I have been a part of the Sakai Accessibility WG for a few years.

Joe Humbert, Assistive Technology and Web Accessibility Specialist
UITS Adaptive Technology and Accessibility Centers
Indiana University, Indianapolis and Bloomington
535 W Michigan St. IT214 E
Indianapolis, IN 46202
Office Phone: (317) 274-4378
Cell Phone: (317) 644-6824
johumber at iupui.edu
http://iuadapts.Indiana.edu/

-----Original Message-----
From: accessibility-bounces at collab.sakaiproject.org [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of Keli Sato Amann
Sent: Friday, March 09, 2012 3:43 PM
To: Beth Kirschner
Cc: cdoherty at stanford.edu; Jacqueline Mai; accessibility at collab.sakaiproject.org WG
Subject: Re: [WG: Accessibility] Which QA server best reflects 2.9? Were accessibility issues filed and addressed?

Hi Beth,
Thank you for your detailed response. Forgive me if this is a silly question, but does the fact that the bells and whistles that were in b01 were not in b02 mean that they definitely didn't make the cut for 2.9, or just that they were temporary removed?

And thank you for the link to the open blocker/critical issues (https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13113), that's going to be useful in general.

Keli
----- Original Message -----
From: "Beth Kirschner" <bkirschn at umich.edu>
To: "Keli Sato Amann" <kamann at stanford.edu>
Cc: "accessibility at collab.sakaiproject.org WG" <accessibility at collab.sakaiproject.org>, cdoherty at stanford.edu, "Jacqueline Mai" <jamai at stanford.edu>
Sent: Friday, March 9, 2012 6:47:37 AM
Subject: Re: [WG: Accessibility] Which QA server best reflects 2.9? Were accessibility issues filed and addressed?

Hi Keli,

   Comments below -- hope this helps!

- Beth

On Mar 7, 2012, at 12:53 PM, Keli Sato Amann wrote:

> Hi Folks,
> I haven't been following this group closely so apologies if this has been discussed. My colleagues Jackie, Christine, and I were looking at QA servers to get a sense of what was coming up for 2.9 so we could prepare for migration. We happened to log into different servers and we noticed that http://sakaicle1-trunk.uits.indiana.edu:8181/portal has all the bells and whistles (for instance, more drag and drop for managing tabs, "add a tool" option directly under navigation) but QA3-US did not. I have three questions:
> 
> 1) Which server more accurately reflects what's going to be in 2.9, assuming everything passes? We noted that sakaicle1-trunk is described as "Setup for Sakai Accessibility Review and 2.9 QA Work" so is that the best server to look at?
> 
It looks like Brian Richwine set up http://sakaicle1-trunk.uits.indiana.edu:8181/portal for "accessibility review", but it's still running the b01 tag.
The http://qa3-us.sakaiproject.org:8086/portal is consistently updated to the latest tag, thanks to Chris Maurer. 
All 2.9 QA servers are listed in confluence (https://confluence.sakaiproject.org/display/QA/QA+Servers+-+Sakai+2.9) -- but you probably already know this :-) The http://sakaicle1-trunk.uits.indiana.edu:8181/portal server is running a b01 tag, and I believe some of the "bells and whistles" you noticed have been removed or disabled in the current b02 tag, in order to address JIRA issues.

**Joe: As Beth stated sakaicle was setup for "accessibility  review."  We are trying to keep it up to date with the current beta tag releases, but have fallen behind.  We will be updating it in the coming days.  I would follow Beth's server recommendations.    

> 2) Were the critical issues that are documented in the 41 pages on https://confluence.sakaiproject.org/display/2ACC/Sakai+2.9+Accessibility+Review+Results ever addressed? I don't see JIRA numbers listed next to all of those issues and there is only one JIRA listed on this page as "to push for 2.9." If those JIRAs were created, is there an easy way to see if they were all addressed?
> 
Open Blocker/Critical issues are listed in JIRA: https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13113 including quite a number of accessibility issues that Brian Richwine wrote up. I'm not sure how these relate to the accessibility review results you mention above.

**Joe:  We are still actually working on the 2.9 accessibility review.  Do to some organizational changes, entering of new Jiras for the 2.9 accessibility review is lagging a little behind.  We will be aggregating all the results, checking against existing Jiras and adding new Jiras as time permits.  The Accessibility WG's goal is to have as many Jiras logged before the 2.9 code freeze as possible.  In addition, the WG will also help to provide fixes for the Jiras we log.  Keep tracking the open issues and the review results page for updated information. To view the complete list of 2.9 accessibility issues and track which issues have been addressed please click the following link: https://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SAK+AND+affectedVersion+in+%28%222.9.0-b02%22%2C+%222.9.0-b01%22%29+AND+component+%3D+Accessibility+ORDER+BY+created+ASC%2C+key+DESC 

> 3) How have critical accessibility issues been dealt with historically for Sakai? Are they blockers for release? Or is this the first comprehensive review that's been done? I suppose each school ultimately is responsible for complying with federal law, but none of us are experts and look to this group for guidance.
> 
Historically and currently, we are wholly dependent on community involvement to resolve any and all issues, and this includes accessibility issues. The accessibility issues are currently listed as "critical" not "blockers". We have a regular Thursday CLE Team t-con at 10am, which is currently focused on the 2.9 release. We would more than welcome your participation and involvement! The t-con connection information and meeting time is announced every week on the sakai-qa at collab.sakaiproject.org and cle-release-team at collab.sakaiproject.org email lists.

**Joe:  I personally have been working with Sakai accessibility since 2007 and version 2.4.  However the WG was doing reviews before I joined and has reviewed and logged new issues in from Sakai 2.0 through 2.9, with full reviews starting at 2.2. The Sakai community has been graciously addressing as many critical accessibility issues as possible with each release. Beth is correct about the level of the accessibility issues.  To view the complete history of reviews please visit https://confluence.sakaiproject.org/display/2ACC/Accessibility+Working+Group#AccessibilityWorkingGroup-evaluating  

> Thanks for your feedback
> Keli Amann
> User Experience Specialist
> Academic Computing Services, Stanford University 
> _______________________________________________
> accessibility mailing list
> accessibility at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/accessibility
> 
> TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
_______________________________________________
accessibility mailing list
accessibility at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/accessibility

TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"