[WG: Accessibility] Sakai 2.7 Accessibility Review Tool Priorities

Fri Jan 29 10:52:52 PST 2010

Thanks Nate!

The accessibility working group hasn't traditionally been involved in the development of Sakai, so we don't have a good feel for where changes have been occurring.

We will add Site Stats and replace Profile with Profile 2. 

Sincerely,
  Brian

-----Original Message-----
From: Nate Angell [mailto:nate.angell at rsmart.com] 
Sent: Friday, January 29, 2010 1:49 AM
To: Sakai Product Council
Cc: accessibility at collab.sakaiproject.org; Richwine, Brian L
Subject: Fwd: [WG: Accessibility] Sakai 2.7 Accessibility Review Tool Priorities

Sakai Product councilors and accessibility review team:

Wanted to make sure the Sakai Product Councilors all saw this list of tools earmarked for accessibility review and added any observations we might have on the choices made here.

You can see the same info wiki form at:
http://confluence.sakaiproject.org/display/2ACC/Sakai+2.7+Accessibility+Review

Personally, I noticed that the major new tools promoted to maintenance status were not earmarked as targets for accessibility review (ie, Site Stats, Profile 2). Profile 2 probably has the highest likelihood of reaching the greatest number of end users.

Other promoted tools-Basic LTI Portlet and Conditional Release-may not have sufficient general user-facing functionality to lift them to even a medium priority for accessibility review.

Sorry for the extra ping if you've already seen and considered this.

Begin forwarded message:

> From: "Richwine, Brian L" <brichwin at indiana.edu>
> Date: January 28, 2010 2:04:09 PM MST
> To: "Whyte, Anthony" <arwhyte at umich.edu>, David Horwitz <david.horwitz at uct.ac.za>
> Cc: "accessibility at collab.sakaiproject.org WG" <accessibility at collab.sakaiproject.org>
> Subject: [WG: Accessibility] Sakai 2.7 Accessibility Review Tool Priorities
> 
> Hello,
> 
> The accessibility working group is getting ready to start an accessibility review of Sakai 2.7. Due to limited resources, we have to focus our efforts to a subset of the Sakai tools. We have picked a set of tools to focus our review on based on tools we know get used most by students and instructors, ones we haven't tested in a while, and on ones we know through various channels have had significant UI changes.
> 
> The tools we are focusing our efforts on are:
>  -High Priority: Chat Room, Forums, and Wiki
>  -Medium: Peferences, Profile, Membership, Account, Worksite Setup, Announcements, Assignments, Calendar Summary, Drop Box, Home, Link Tool, Messages, Post 'Em, Presentations, Resources, Schedule, and Syllabus
> 
> Gonzalo suggested that we contact you in your role as a release manager and see if there are any tools we are overlooking that deserve attention in our review.
> 
> Thanks,
>  Brian Richwine
> 
> 
> 
> -----Original Message-----
> From: Silverio, Gonzalo [mailto:gsilver at umich.edu] 
> Sent: Thursday, January 21, 2010 8:58 AM
> To: Richwine, Brian L
> Cc: accessibility at collab.sakaiproject.org; Whyte, Anthony; David Horwitz
> Subject: Re: [WG: Accessibility] Sakai 2.7 Accessibility Review Concerns
> 
> Hi,
> 
> The core tools have not changed all that much in 2.7 (excluding Forums,
> perhaps Wiki). 
> 
> I think Anthony Whyte <arwhyte at umich.edu> and/or David Horwitz
> <david.horwitz at uct.ac.za> will have (as release managers) a good idea of the
> degree of change across all the functionality that is going into 2.7. I have
> ccd them here. Extrapolating from the JIRAs and commits might help surface
> where things have changed, but they would know for sure.
> 
> Thanks.
> 
>    -Gonzalo
> 
> On 1/20/10 5:37 PM, "Richwine, Brian L" <brichwin at indiana.edu> wrote:
> 
>> Hello Gonzalo,
>> 
>> The accessibility WG is working on the Sakai 2.7 Accessibility Review, and
>> Mike Elledge suggested I contact you to see if you knew which tools were new
>> or have undergone significant changes for the 2.7 release.
>> 
>> Sincerely,
>>  Brian Richwine
>> 
>> 
>> 
>> -----Original Message-----
>> From: Michael S Elledge [mailto:elledge at msu.edu]
>> Sent: Wednesday, January 20, 2010 5:24 PM
>> To: Richwine, Brian L
>> Subject: Re: [WG: Accessibility] Sakai 2.7 Accessibility Review Concerns
>> 
>> Hi Brian--
>> 
>> I think taking a "triage" approach makes the most sense. That's how
>> we've approached it in the past, i.e., reviewing only new tools or tools
>> with substantive changes.
>> 
>> You may want to send a note to Gonzalo Silverio--in the past he would
>> let us know where the major changes had taken place. He may still keep
>> track of those things...
>> 
>> Mike
>> 
>> Richwine, Brian L wrote:
>>> 
>>> Hi,
>>> 
>>> In preparation of writing Alan Berg (Sakai's Interim QA Director)
>>> about performing the Sakai 2.7 Accessibility Review, I discovered that
>>> we are quite late in starting the review. I am not sure if the release
>>> timeline found in the release practice guidelines [1] is being
>>> followed, but according to it, accessibility testing should have begun
>>> at 24 weeks prior to the release. Yesterday I saw message on the Sakai
>>> Announcements list that published the Draft 2.7.0 Release Schedule [2]
>>> and gives a release date of 22 April 2010 for Sakai 2.7. April 22nd is
>>> only 13 weeks from now.
>>> 
>>> A past critique of the Accessibility Reviews has been that they come
>>> too late in the release process and only the easiest of accessibility
>>> issues found could hope to be fixed before the release. Since the
>>> Accessibility Reviews focused on tools worthy of release
>>> consideration, the tools' designs are already very established and
>>> accessibility issues cemented into those designs were unlikely to be
>>> addressed. If the Sakai 2.7 Accessibility Review is indeed quite late,
>>> does the group think the review as we have in the past would still be
>>> of value and worth doing given our finite resources and a strong
>>> desire to participate in the early design of Sakai 3?
>>> 
>>> I think the review would have value in checking any new tools, and in
>>> looking for new issues or improvements in the tools that have changed
>>> significantly. This would help us update the Sakai Current
>>> Accessibility page, the accessibility help page, and update/add Jira
>>> tickets.
>>> 
>>> Footnotes:
>>> 
>>> [1]
>>> http://confluence.sakaiproject.org/display/REL/Release+Practice+Guidelines#Re
>>> leasePracticeGuidelines-ReleaseTimeline
>>> 
>>> [2]
>>> http://collab.sakaiproject.org/pipermail/announcements/2010-January/000187.ht
>>> ml
>>> 
>>> -Brian
>>> 
>>> Brian Richwine**
>>> 
>>> Adaptive Technology Support Specialist**
>>> 
>>> Adaptive Technology and Accessibility Centers**
>>> 
>>> Indiana University - Bloomington/Indianapolis**
>>> 
>>> http://iuadapts.indiana.edu**
>>> 
>>> (812) 856-4112**
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> _______________________________________________
>>> 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"