E-mailWeb Accessibility Compliance
Please note that the compliance pages refer to the Sakai Enterprise tools and not provisional tools such as OSP, which have not been evaluated for accessibility.
- Section 508 Compliance
- WCAG 1.0 Compliance
- Voluntary Product Accessibility Template (VPAT)
Sakai 2.6 Accessibility Issues and Enhancements
Sakai 2.6 is accessible to persons using most adaptive technology, although it has several issues we are continuing to address.
Accessibility Issues and Jira
As we find problems, we put them in the Jira queue for repair. Several critical issues remaining to be resolved: the WYSIWYG editor does not provide a keyboard-based exit from the text input box and Sakai does not enlarge well beyond 2x (a frame problem)
Note: The list may contain some items that do not relate to accessibility, due to Jira's text based search mechanism.
Accessibility Issues
Frames
Sakai currently has an iFrame for page content. We are hoping to provide a frameless version of Sakai in the near future, which would improve usability for persons using screen magnifiers. Also, tools that are refactored to be JSR-168 compliant will work without frames. A schedule for either implementation has not been established.
JavaScript
Sakai relies on JavaScript for some basic top of page operations, including setting permissions and options. It is our understanding that javascript will be permitted under the upcoming WCAG 2.0 guidelines, so at this point we have chosen not to provide alternative, non-script functionality. Instead we will note within the Accessibility page in help that JavaScript needs to be enabled (per WCAG 2.0 baselines) for Sakai to work.
You can view other general issues:
Accessibility Enhancements
Making Accessibility Usable
We have also included a variety of skip links, accesskeys, headings, titles, form and table attributes, and utilized stylesheets in Sakai 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.
Future Enhancements
Some tools rely on Java Server Face (JSF) widgets. Although they incorporate accessibility attributes, it is best to customize JSF widgets to make them fully WCAG compliant. This will be done as time and resources permit. University of Toronto is working on an interface that will enable users to customize Sakai presentation (such as enlarged text, white font on black background, etc.). And there are plans to introduce a content repository and device-dependent authoring system piloted by the University of Toronto. Sakai 2.4 contain provisional tools that do not require iFrames, and can serve as templates for future iFrame-free development (written using JSR-168).
