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

[Beth Kirschner]

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.

> 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.

> 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.


> 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"