Date: December 14, 2015
Product Name: Mobius SLIP
Product Version: 2.7 and later
Vendor Company Name: Complex Task Assessment Solutions and Information Technology LLC (DBA Social Learning Solutions)
Vendor Contact: info@mobiusSLIP.com

Summary Table VPAT™ Voluntary Product Accessibility Template®
Criteria	Level of Support and Supporting Features	Remarks and Explanations
Section 1194.21 Software Applications and Operating Systems	Supports
Section 1194.22 Web-based Internet Information and Applications	Supports
Section 1194.23 Telecommunications Products	Not applicable
Section 1194.24 Video and Multi-media Products	Not applicable
Section 1194.25 Self-Contained, Closed Products	Not applicable
Section 1194.26 Desktop and Portable Computers	Not applicable
Section 1194.31 Functional Performance Criteria	Supports through equivalent facilitation
Section 1194.41 Information, Documentation and Support	Supports

 

Section 1194.21 Software Applications and Operating Systems – Detail VPAT™ Voluntary Product Accessibility Template®
Criteria	Level of Support and 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	This application is designed to run on a system that has a keyboard, and all actions are executable from the keyboard. The result of a function can be discerned textually.
(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	No controls or other GUI elements in the application are known to cause disruption or disable activated features of other products or of the local operating system that are accessibility features.
(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	The application is designed so that the current focus provided moves among the interactive interface elements as the input focus changes and allows it to be programmatically exposed so that Assistive Technology can track focus and focus changes.
(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	Sufficient information about the user interface element including the identity, operation and state of the element can be utilized by the Assistive Technology.
(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	Bitmap images which used to identify controls, status indicators and their meanings are consistent throughout the application’s performance.
(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	Textual information is provided through any common and current version of web browser.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.	Supports	This application does not override any user selected contrast or color selection or any individual display attributes.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.	Supports	No animation is used for displaying information.
(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	All relevant information is displayed as either text or numbers. Color coding is used consistently and only as a supplementary aid for users having difficulty comprehending and interpreting textual or numeric data.
(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.	Supports	This application does not permit users to adjust color and contrast setting within itself but uses the local computer system’s settings instead.
(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	This application does not use flashing or blinking text or objects or any 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	All electronic forms in this application allow individuals using Assistive Technology to access the information, field elements, and functionality required for the completion and submission of the form, including all directions and cues.

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.

 

Section 1194.22 Web-based Internet information and applications – Detail VPAT™ Voluntary Product Accessibility Template®
Criteria	Level of Support and 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	All relevant system images in the application have text equivalents. Diagrams and controls that have an equivalent tabulated text representation use alt=””. Decorative images use alt=””. All text in the icons used in the student interface is unique and identifies which object the action applies to. Exceptions: Some text in the icons in the instructor interface is not unique. Users control their own content. Therefore, the content of the files attached or referenced by users through URL may include visual data without equivalent text or audio representation. Users have the option to download files.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	Supports with exceptions	The application interface does not use built-in multimedia presentations. Exceptions: Users control their own content and are responsible for ensuring its 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	Color is used to differentiate warning and information/confirmation messages. The text of the messages clearly differentiates them as well. Tool menus and tabs use color/highlighting to indicate current location. This data is also communicated by headings and selected states.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.	Supports	Style sheets are only used in visual design. A user or screen reader can read pages with the associated style sheets disabled. Pages use logical HTML structures to ensure navigability when style sheets are disabled (headings, contextualized unique links, table headings and summaries, logical tab order and focus).
(e) Redundant text links shall be provided for each active region of a server-side image map.	Not applicable	The application does not use server-side image maps.
(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	The application does not use server-side image maps.
(g) Row and column headers shall be identified for data tables.	Supports	Data tables, such as the list of assignments and their due dates in the Course Summary page, are labeled with informative column and row headers.
(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.	Not applicable	The application has no data tables with two or more logical levels of row or column headers.
(i) Frames shall be titled with text that facilitates frame identification and navigation.	Not applicable	The application does not use frames.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.	Not applicable	The application does not cause the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
(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.	Supports	Accessibility features are integrated into the standard application interface; a text-only version is unnecessary.
(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	The application uses javascript, WAI-ARIA and the most modern HTML5 technology to provide feedback from interactive elements and to allow Assistive Technology, such as screen readers, to render information back to the user.
(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).	Supports	The application does not require any applet or plug-in to work with its default functionality. Users can upload their own multimedia content using Flash, but if users do not have Flash installed on their computer, they will be prompted with a link to download Flash.
(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	All forms in the application are accessible by keyboard and assistive technologies (such as Microsoft Narrator, Chrome Vox, JAWS, NVDA or VoiceOver). Users are warned when a link opens in a new window.
(o) A method shall be provided that permits users to skip repetitive navigation links.	Supports	The application also uses semantic HTML5 elements, such as “nav”, “aside” and “footer”, as well as ARIA landmark roles, such as “navigation”, “complementary”, “main” and “contentinfo” to cue Assistive Technology.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	Supports	For all timed responses users are alerted by email in advance of the deadline. Deadline calendar can be exported as an iCalendar file to another calendar client to set up the alerts.

 

Section 1194.31 Functional Performance Criteria – Detail Voluntary Product Accessibility Template® VPAT™
Criteria	Level of Support and 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 through equivalent facilitation	Windows Narrator supports the functional needs of users with no or usable low vision if the application is open in Internet Explorer or Microsoft Edge. Chrome Vox supports the functional needs of users with no or usable low vision if the application is open in Google Chrome.
(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 through equivalent facilitation	Windows Narrator supports the functional needs of users with no or usable low vision if the application is open in Internet Explorer or Microsoft Edge. Chrome Vox supports the functional needs of users with no or usable low vision if the application is open in Google Chrome. The application supports screen magnification and browser-provided zoom functionality.
(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	No audio information is required to operate the application. No information retrieval requires 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 provided.	Not applicable	No audio information is required for operation of the application. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.
(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.	Not applicable	Speech is not required to operate of the application.
(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	No simultaneous actions or fine motor control are required to operate the application beyond conventional use of keyboard, mouse or touchscreen.

 

Section 1194.41 Functional Performance Criteria – Detail Voluntary Product Accessibility Template® VPAT™
Criteria	Level of Support and 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	All user documentation is available on the website (as HTML pages) accessible through Assistive Technology.
(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	Available upon request and will be provided on the website.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities.	Supports	Online support is available by email.

← Refund Policy Privacy Policy →