Sakai 2.7 VPAT

Explanation of Response Options

Supports	Use this language when you determine the product fully meets the letter and intent of the Criteria.
Supports with Exceptions	Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
Supports through Equivalent Facilitation	Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
Supports when combined with Compatible AT	Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
Does not Support	Use this language when you determine the product does not meet the letter or intent of the Criteria.
Not Applicable	Use this language when you determine that the Criteria do not apply to the specific product.
Not Applicable	Fundamental Alteration Exception Applies Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

Summary Table

*Criteria*	Supporting Features	Remarks and explanations
Section 1194.21 Software Applications and Operating Systems	Supported	See Response Section
Section 1194.22 Web-based Internet Information and Applications	Supported	See Response Section
Section 1194.23 Telecommunications Products	Not Applicable	Not included in document
Section 1194.24 Video and Multi-media Products	Not Applicable	Not included in document
Section 1194.25 Self-Contained, Closed Products	Not Applicable	Not included in document
Section 1194.26 Desktop and Portable Computers	Not Applicable	Not included in document
Section 1194.31 Functional Performance Criteria	Supported	See Response Section
Section 1194.41 Information, Documentation and Support	Supported	See Response Section

Section 1194.21 Software Applications and Operating Systems – Detail

*Criteria*	Supporting Features	Remarks and explanations
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.	Supports	Tab navigation is enabled. Three "skip to content links" with accesskeys are provided which enable quick navigation to major sections of the Sakai interface. The rich text editor has basic WYSIWYG shortcuts (e.g. bold = cntrl +b in windows)
(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.	Supports with exceptions	Sakai works well with the page magnification features as found in modern Web browsers. The icons in the FCKEditor WYSIWYG editor and many icons in the Sakai interface disappear when the Microsoft Windows OS's Highcontrast mode is enabled.
(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes.	Supports	Sakai uses the windows standard cursor and highlight for controls, and identifies through visual and textual cues which tools are being used at a given time. Care has been taken in creating the default Sakai CSS files that the default visual indication of keyboard focus has been maintained. Adopting institutions need to be careful when skinning Sakai's CSS files to maintain visible indication of focus (do not reset the outline property on focusable elements).
(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text.	Supports with exceptions	The FCKeditor WYSIWYG editor icons are not accessible. Most button icons in Sakai's interface are accompanied by text and/or also display a text description when a mouse is positioned over the icon. All icons in Sakai have alternative text descriptions that are available to Assistive Technologies.
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.	Supports with exceptions	Sakai maintains a consistent use of bitmap images / icons throughout the majority of its native tools. Third party tools provided for institutions through an integration may have additional or duplicate buttons within their user interface which are not consistent with Sakai.
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.	Supports
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.	Supports with exceptions	The icons in the FCKEditor WYSIWYG editor and many icons in the Sakai interface disappear when the Microsoft Windows OS's Highcontrast mode is enabled.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.	Not Applicable	Animation is not employed in Sakai's user interface. Content authors need to make sure the content they upload is accessible.
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.	Supports	Color Coding is used as a supplemental effect only. Required fields in Sakai are marked by “*” to so that color is not the sole differentiation.
(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.	Not Applicable	Sakai does not allow the user to adjust color and contrast settings. Color choices are set by the CSS files and may be customized by the adopting institution.
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.	Supports	Sakai does not use flashing or blinking text, objects, or other elements.
(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.	Supports with exceptions	Forms relying on the FCKeditor / WYSIWYG editor are not accessible to many assistive technology users

Section 1194.22 Web-based Internet information and applications – Detail

*Criteria*	Supporting Features	Remarks and explanations
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).	Supports with exceptions	Sakai provides <alt> descriptions where images provide relevant information and <alt=””> where images are purely decorative. Exception: Non-descriptive label contained in Page Order Helper tool (SAK-11672, 11669).
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	Not Applicable	Sakai does not contain multimedia presentations. However, authors may choose to upload multimedia files and are responsible for their accessibility.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.	Supports	Required fields in Sakai are marked by “*” to so that color is not the sole differentiation.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.	Supports	Sakai content and navigation are not dependent on CSS for readability.
(e) Redundant text links shall be provided for each active region of a server-side image map.	Not Applicable	There are no server-side image maps in Sakai.
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.	Not Applicable	There are no client-side image maps in Sakai.
(g) Row and column headers shall be identified for data tables.	Supports	Sakai identifies row and column headers either through the <th scope> or <th><id> attributes.
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.	Supports	There are no complex tables in Sakai.
(i) Frames shall be titled with text that facilitates frame identification and navigation	Supports with exceptions	Sakai provides meaningful frame titles to differentiate subject title and content. Exception: Frame title missing in My Workspace (SAK-11415), Chat (SAK-11423).
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.	Supports	There are no flickering images in Sakai.
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.	Not Applicable	Compliance can be achieved in Sakai without the use of text-only pages.
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.	Supports with exceptions	JavaScript and related technologies used in Sakai are evaluated for accessibility using JAWS. Exception: There is a Flash object in the Wiki tool that is inaccessible, even though it does not contain relevant content.
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).	Not Applicable
(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.	Supports	Sakai uses <label for> and <id> elements to make forms accessible. Standard html markup is used for form actions.
(o) A method shall be provided that permits users to skip repetitive navigation links.	Supports	Sakai provides skip links to worksites, tools and page content.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	Supports with exceptions	Users are notified in advance of when Sakai will be closed due to inactivity through a DHTML popup. However, the appearance of that popup (and its contents) is not automatically announced by assistive technologies we've tested and may go unnoticed.

Section 1194.31 Functional Performance Criteria – Detail

*Criteria*	Supporting Features	Remarks and explanations
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.	Supports when combined with compatible AT	Text/Jaws Screen Reader?	Vision
(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.	Supports when combined with compatible AT	Text/Jaws Screen Reader?	Vision
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided	Supports	Text is the dominant form of content communication and interaction in Sakai.	Hearing
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.	Not Applicable	Audio and Audio/Visual content is predominantly provided through third party applications chosen by the institution. Refer to vendors for additional information. Where links to external audio content is provided, compliance depends on the objects chosen by instructor. ASSISTIVE HEARING DEVICES?	Hearing
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.	Supports	Note: many virtual meeting platforms offer text chat capability during the meeting.	Speech
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.	Supports	Keyboard and Mouse are used for navigation and entry without requiring simultaneous action. Any special devices configured for accessibility, and compatible with the web browser used to access Sakai will function in Sakai. Other options???	Motor Control or Simultaneous Actions

Section 1194.41 Information, Documentation and Support – Detail

*Criteria*	Supporting Features	Remarks and explanations
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge	Supports
(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.	Supports
(c) Support services for products shall accommodate the communication needs of end-users with disabilities.	Supports	Sakai Commercial Affiliates, like rSmart, provide Tier 2 and Tier 3 support both online (text form), and by telephone.