Skip to end of metadata
Go to start of metadata
Sakai Accessibility and Usability Teleconference
April 22, 2010
- Mary Stores
- Brian Richwine
- Scott Williams
- Apple Suwannawut
- Gonzalo Silverio
- Sean Keagan
Jira Ticket Activity
- Due to a busy semester, Scott has only done one Jira ticket.
- Regarding outstanding Jira tickets, Mary and Brian are still verifying that some of the issues have been fixed, or that there are still accessibility issues for the remaining tickets.
- Mary and Brian will begin writing Jira tickets within the next week for issues found in Sakai 2.7.
Getting involved in Sakai 3
- Brian send e-mail to Eli to see about what stage of development Sakai 3 is in.
- Silverio recommends going ahead and delving into it in order to start testing.
- There has been a comment from Christian requesting a video about screen-reader navigation in Sakai 3. The video would highlight some accessible and inaccessible features of Sakai 3.
Moving on from Sakai 2.7
- The 2.7 cycle is closed.
- Gonzalo's time is getting shorter, so he won't be able to spend as much time as he has in the past.
- Remaining accessibility issues should be retargeted to 2.71; Alan Berg is in charge of the QA process, Brian will e-mail him.
- Charles Hedrick is the guy in Syracuse who wants to deal with the inconsistencies in tools. He believes there should be more uniformity in the way the tools are designed/tool layout.
Maintenance team repairs
- It can be a point release if the accessibility issue doesn't interfere with functionality, if it doesn't interfere with documentation.
- You can introduce a new way of functionality if it is optional. For example adding live ARIA to chat doesn't change the behavior, so this is a good candidate for maintenance release.
Important topic for next teleconference
- Add the June Sakai conference to the agenda. Mary, Eli, and Brian will be presenting, so it would be good to get ideas from the group.