Joshua Hori, UC Davis, (firstname.lastname@example.org); Scott Williams, University of Michigan, (email@example.com); Gonzalo Silverio, University of Michigan, (firstname.lastname@example.org); Mike Elledge, Michigan State. (email@example.com); Joe Humbert, Indiana University, (firstname.lastname@example.org); Apple Suwannawut, graduate student, Indiana University, (email@example.com); Margaret Londergan, Indiana University, Chair, (firstname.lastname@example.org). Tried to attend but ports all taken: Kirk Alexander, UC Davis, (email@example.com)
August 13, 2009. Contact information: 812-856-3600; conference code: 002264#
Great meeting and discussion. A most heartfelt thanks to all who participated. Here are the action items stemming from our conversation today:
The original developers' accessibility checklist will be reviewed by Gonzalo to be updated and expanded as necessary for Sakai 3.0. Focus will be on AJAX and other web 2.0 accessibility issues. He will send out a list of items that need to be altered, added or dropped from the checklist.
Everyone will review Mike Elledge's helpful email and especially the embedded links to the Fluid user experience testing templates and protocols to:
a. See if these can be used by the SAKAI accessibility working group for accessibility testing.
b. See if additions need to be made to make them more useful for accessibility testing.
(See email attachment.)
Margaret will make contact with the leader of this working group to further cooperation between this group and the AWG.
Accessibility testing will continue for SAKAI 2.6 and beyond. Gonzalo pointed out that although SAKAI 3.0 is coming, it may be quite a while until it is adopted by institutions. Therefore, it remains important to continue accessibility testing of current and upcoming (2.7) releases.
To get all the testers on the same page, during the next two weeks the following will take place:
a. Confirm the testing template that will be used
b. It is exciting to have accessibility testers from both University of Michigan offered by Scott and UC Davis offered by Joshua. Between now and the next meeting Joshua and Scott will identify testers in addition to themselves who could perform accessibility testing and the specific adaptive technology the user would use to do the testing. Joe Humbert will send Scott and Joshua links to the pages where testers can sign up for testing.
c. Determine whether there are funds to pay testers (MDL) and how they will be administered.
d. Determine what the testing procedure is. Everyone test for all items using same testing template? Each school pick a tool to test and report on the accessibility of that tool indicating what adaptive software was used for testing? Other possibilities? Suggestions please.
Gonzalo suggested that an accessibility score card for the tools which are developed by different institutions be created. This could be an effective way of encouraging schools to pay more attention to issues of accessibility for the tools they are developing.
Joe will review current Jira tickets and the previous list of the top ten accessibility issues for SAKAI tools. He will report back on status of and response to Jira tickets that have already been submitted including whether/which top 10 issues have been addressed. This report will help us in identifying the next top issues.
This issue goes two ways. First, the SAKAI community needs to have their awareness of the importance of accessibility heightened. MDL will talk with M. Korkuska to elicit his top down support. Second, developers need encouragement and information that will make it easier for them to include good accessibility development practice. The Accessibility WG will work to further better communication with the developers.
IU has added a member to the Accessibility WG to assist with administrative and other tasks.
Discuss Sean Keegan's exchange with Gonzalo regarding adding issues related to form structure to the accessibility checklist.