Voluntary Product Accessibility Template
Web Content Accessibility Guidelines 2.0 Level A and AA
Voluntary Product Accessibility Template® (VPAT) Version 1.0 – May 2021
This Voluntary Product Accessibility Template, or VPAT, is a tool that helps officials and decision-makers to evaluate SlideRoom design conformance with the accessibility standards under Act World Wide Web Consortium’s Web Content Accessibility Guidelines (WCAG 2.0)) Level A and AA standards.
Vendor: Liaison International
Name of Product: SlideRoom
Product Description: SlideRoom is a cloud-based portfolio management platform that provides users with tools to streamline their admissions processes.
Version: May 2021
Point of Contact Name/Email: Nicole Hunt, Product Manager (nhunt@liaisonedu.com)
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation./li>
- Partially Supports: Some functionality of the product does not meet the criterion./li>
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
VPAT Summary Table
| Criteria | Supporting Features | Remarks and Explanations |
|---|---|---|
| Section 1194.21 Software Applications and Operating Systems | Not Applicable | |
| Section 1194.22 Web-based Internet Information and Applications | Supports | See Detail |
| 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 | See Detail |
| Section 1194.41 Information, Documentation, and Support | Supports | See Detail |
Section 1194.22 Web-based Internet Information and Applications Detail
| Criteria | Conformance Level | Supporting Features |
|---|---|---|
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Supports | SlideRoom provides text equivalents for all non-text elements. The full range of methods is employed including “alt,” “longdesc, ” and element content. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supports | SlideRoom does not require multimedia presentations be consumed by users as part of the process. |
| (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 | SlideRoom does not require rely on color convey information. When color is used (like validation), it always uses a symbol to aid scanning. Also, all contextual links are underlined. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supports | The physical order of the items in the document is the same as the logical order on the page. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not Applicable | SlideRoom does not rely on 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 | SlideRoom does not rely on image maps. |
| (g) Row and column headers shall be identified for data tables. | Supports | Tables are created with semantic html, where all tables, row and column headers are identified. |
| (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 | Tables are created with semantic html, where all tables, row and column headers are identified. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation | Not Applicable | SlideRoom does not rely on 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. | Supports | SlideRoom does not employ any elements that cause screen flickr (like animated gifs, blink tags, etc...). |
| (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 textonly page shall be updated whenever the primary page changes. | Supports with exceptions | SlideRoom does not believe a “separate but equal site” provides a truly accessible experience. So, the system has been made to be fully accessible within an integrated setting. Any reports to the contrary would be addressed quickly. |
| (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 | All content and UI elements generated by a script can be read by Assistive Technology. Whenever new content is surfaced or changed within the application in reaction to a user interaction, two methods are employed: 1) The application will shift keyboard and screen reader focus to the newly changed content. 2) In cases where the newly-surfaced content is temporal and not readily actionable (e.g. auto-save messages), SlideRoom will use ARIA Live regions to read back the updated content to screen-reader users. For users with assistive technologies that do not support ARIA, we provide controls that will surface that content when activated (e.g., a Save button). |
| (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 | SlideRoom does not rely on applets, plugins or other applications to interpret page content. |
| (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 within SlideRoom are accessible to people using Assistive Technology to access field elements, required/optional status, and a pattern of validation that provides a summary at the top of the form with links back to incomplete questions. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Supports | Because SlideRoom manages user focus, users are not confronted repetitive navigation links. |
| (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 alerted to all time-based constraints. Deadline dates are featured prominently throughout the application. When a deadline is less than a week away, the deadline is featured in bold, red text. In addition, SlideRoom uses ARIA Live Regions to read back the deadline date when a screen-reader is not actively reading |
| Remarks: As institutions require hard submission deadlines for all applications, the same is true for applications handled by SlideRoom on behalf of those institutions. As such, all SlideRoom functionality related to submitting an application to an academic institution is governed by a time-based deadline that cannot be modified by users. SlideRoom has introduced several methods to mitigate those issues. |
Section 1194.31 Functional Performance Criteria Detail
| Criteria | Conformance Level | Supporting Features |
|---|---|---|
| (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 | Assistive Technology can be used to provide audio equivalents of all UI elements including menu bars, buttons, dialog fields, validation, instructions, and so forth. |
| (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 | All text throughout SlideRoom is resizable using standard browser controls. SlideRoom is in compliance with WCAG 2.0 Level AA color contrast guidelines, which require a contrast ratio of 4.5:1 for normal text and 3:1 for large text. UI elements are also speakable using screen readers. |
| 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 | SlideRoom does not require user hearing for operation and information retrieval. |
| (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 | SlideRoom does not have any audio elements to be captioned. |
| (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 | All modes of operation and information retrieval in SlideRoom is independent of user 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 | Users can perform all operations and retrieve information through the keyboard using non simultaneous actions. |
Section 1194.41 Information, Documentation and Support Detail
| Criteria | Conformance Level | Supporting Features |
|---|---|---|
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. | Supports | Users can view SlideRoom’s accessibility statement here: http://slideroom.com/docs/accessibility_statement which provides a description of accessibility and compatible features. They may also receive assistance at no charge by emailing accessibility@slideroom.com |
| (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 | Users can view SlideRoom’s accessibility statement here: http://slideroom.com/docs/accessibility_statement which provides a description of accessibility and compatible features. They may also receive assistance at no charge by emailing accessibility@slideroom.com |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. | Supports | Users can view SlideRoom’s accessibility statement here: http://slideroom.com/docs/accessibility_statement which provides a description of accessibility and compatible features. They may also receive assistance at no charge by emailing accessibility@slideroom.com |