Sakai 2.5 is accessible to persons using adaptive technology, although it has several issues we are addressing for the next version.
1. Frames. Sakai currently separates tool titles from content, resulting in each tool page being presented in two frames. This is annoying and results in redundant descriptions of page titles. We are, for lack of a better phrase, working on "merging" the two components to eliminate the problem.
3. Compliance with Requirements. The Sakai Accessibility Style guide was developed early in the project to exceed WCAG 1.0 Priority One and Two Recommendations (see http://bugs.sakaiproject.org/confluence/display/2ACC/Sakai+Accessibility+Guidelines). The style guide was used in developing the latest version of most Sakai tools, and, for the most part, the style guide was followed closely. We review each version (see http://bugs.sakaiproject.org/confluence/display/2ACC/2.0x+Accessibility+Testing+Protocol for protocol), to determine how closely we have met Section 508 Requirements and WCAG Priority One and Two. As we find problems, they are added to the Sakai bug list for resolution (see http://confluence.sakaiproject.org/confluence/display/2ACC/Accessibility+Issues+in+Jira for known bugs).
4. Making Accessibility Usable. We have also included a variety of skip links, accesskeys, headings, titles, form and table attributes, and utilized stylesheets to improve usability for adaptive technology (AT) users. For a description of how to take advantage of them, please take a look at the Accessibility section in Sakai Help.
5. Future Challenges. In upcoming versions of Sakai we will face additional challenges as we move to a Web 2.0 interface. As a result, Sakai designers and developers are participating in the Fluid project (see http://fluidproject.org/), an open source initiative to develop accessible, interactive components for Sakai and other open source course management systems.
Please let us know if you have come across other issues that we may have overlooked.
Last revised January 23, 2008