Accessibility
At Unicheck, we believe that Accessibility is intended not only for people with disabilities, but also for all of us who are grateful that there are no obstacles to using our abilities.
Our Approach to Accessibility
We strive to make accessibility a key factor, from the very early stages of product development to release. Our central accessibility team is authorized to monitor the availability status of Unicheck products and coordinate training, testing and consulting on accessibility issues. Product teams are trained to help incorporate accessibility into product design and release. We also strive to develop relationships with various users and protection groups in order to get feedback.
Voluntary Product Accessibility Template (VPAT)
To educational institutions, companies and government agencies have been easier to comply with accessibility standards, we provide transparent information about how our products currently work for people with disabilities. We offer the following voluntary product accessibility templates (VPAT). This document is a tool that administrators and decision-makers can use to evaluate Unicheck conformance with the accessibility standards under Section 508 of the Rehabilitation Act and the Act WCAG 2.0 AA Standards. We will continue to update this site as additional VPAT documentation becomes available.
Unicheck Web Content Accessibility Guidelines (WCAG 2.0) Checklist
This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Unicheck conformance with the WCAG 2.0 standards, level AA.
Name of Product: Unicheck
February 18, 2019
WCAG 2.0 Guidelines
Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
| CRITERIA | SUPPORTING FEATURES | REMARKS AND EXPLANATIONS |
|---|---|---|
| 1.1 Text Alternatives: Provide text alternatives for any non-text content. Some elements do not have appropriate text alternatives. | Supports with exceptions | Some elements do not have appropriate text alternatives. |
| 1.2 Time-based Media: Provide alternatives for time-based media. | N/A | Unicheck does not hold time-based Media. |
| 1.3 Adaptable: Create content that can be presented and navigated in different ways. | Supports | Reading and navigation order is usually logical and intuitive. |
| 1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background. | Supports | Color is not used as the sole method of conveying content. |
Principle 2: Operable
User interface components and navigation must be operable
| CRITERIA | SUPPORTING FEATURES | REMARKS AND EXPLANATIONS |
|---|---|---|
| 2.1 Keyboard Accessible: Make all functionality available from a keyboard. | Supports | All content is a keyboard accessible. |
| 2.2 Enough Time: Provide users enough time to read and use content. | Supports | Unicheck does not hold time-sensitive content. |
| 2.3 Seizures: Do not design content in a way that is known to cause seizures. | Supports | Content does not flash. |
| 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are. | Supports with exceptions | Heading structure is present, though not always complete. |
Principle 3: Understandable
Information and the operation of user interface must be understandable.
| CRITERIA | SUPPORTING FEATURES | REMARKS AND EXPLANATIONS |
|---|---|---|
| 3.1 Readable: Make text content readable and understandable. | Supports | Pages have a specified language. |
| 3.2 Predictable: Make web pages appear and operate in predictable ways. | Supports | For the most part, navigation is consistent throughout the application. |
| 3.3 Input Assistance: Help users avoid and correct mistakes. | Supports | Important labels and instructions are always accessible. |
Principle 4: Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
| CRITERIA | SUPPORTING FEATURES | REMARKS AND EXPLANATIONS |
|---|---|---|
| 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies. | Supports with exceptions | HTML validation issues do not impact accessibility. ARIA attributes are sometimes incorrect, which can present incorrect roles, states, or properties to screen reader users. |
Section 508 of the Rehabilitation Act
Name of Product: Unicheck
February 18, 2019
SECTION 1194.21 SOFTWARE APPLICATIONS AND OPERATING SYSTEMS – DETAIL VPAT™ VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE®
| 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 | We strive to make sure all sections of Unicheck can be navigated and controlled with only a keyboard. |
| (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 | Unicheck does not interfere with any operating system or browser shortcuts. Accessibility features such as sticky keys, magnifiers, screen readers, cursor sizes and virtual keyboards are not disabled or disrupted by Unicheck. |
| (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 | Where possible, Unicheck uses default browser focus styles. Where those styles are overridden, Unicheck provides distinct focus styles. |
| (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 | Provided by the browser. |
| (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 | Unicheck uses icons to help depict the purpose of certain interface elements, such as "+" add buttons. The use of these icons is consistent throughout the site. Whenever a single graphic is used, such as a lone "+" graphic, alt text or CSS text replacement is used to enable screen readers to read the purpose of the link/button to the user. |
| (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 | Provided by the browser. |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Not applicable | |
| (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 | |
| (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 | Unicheck does not use color alone to distinguish the importance of a visual element. |
| (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 | The interface of Unicheck has been styled with CSS to comply with Section 508's contrast and color settings. |
| (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 | Unicheck does not use flashing or blinking text. |
| (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 | Unicheck and all forms in the application work well with screen readers such as JAWS or VoiceOver. |
SECTION 1194.22 WEB-BASED INTERNET INFORMATION AND APPLICATIONS – DETAIL VPAT™ VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE®
| 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 | Meaningful images in the Unicheck user interface have alt-text descriptions. Non-relevant images have no alt-text. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supports | Unicheck does not contain built-in multimedia presentations. Users upload their own content and are responsible for ensuring the accessibility of the uploaded content. |
| (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 | Unicheck does not use color alone to distinguish the importance of a visual element. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supports | A user or screen reader can read and understand pages in Unicheck with the associated style sheets disabled. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Supports | Unicheck 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. | Supports | Unicheck does not use server-side image maps. |
| (g) Row and column headers shall be identified for data tables. | Supports | All data tables have row and column headers, however div markup is used inside the interface. |
| (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 is a drop down area related to the row that reveals more information when clicked. The elements in this area fall directly under the main table structure. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation | Supports | Unicheck 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. | Supports | Unicheck 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 | Unicheck is compliant with all provisions of this section, so 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 | Unicheck uses javascript, WAI-ARIA and the most modern HTML5 techniques to provide feedback from interactive elements and to allow Assistive Technology such as screen readers to read and transmit 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 | Unicheck does not require any applet or plug-in to work with its default functionality. |
| (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 | Unicheck and all forms in the application work with screen readers such as JAWS, NVDA or VoiceOver. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Supports | Unicheck does not have 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 | Unicheck has no action that requires a timely response. |
SECTION 1194.31 FUNCTIONAL PERFORMANCE CRITERIA – DETAIL VPAT™ VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE®
| 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 | Unicheck has been optimized to work well with screen readers such as JAWS or VoiceOver. |
| (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 | Unicheck 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 | Unicheck does not require hearing for operation. |
| (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. | Supports | Unicheck does not use any audio for its default operation. 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. | Supports | Unicheck does not require speech for operation. |
| (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 | Unicheck does not require fine motor control or simultaneous actions. It is accessible via keyboard. |
SECTION 1194.41 INFORMATION, DOCUMENTATION AND SUPPORT – DETAIL VPAT™ VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE®
| 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, with exceptions | Product support in an accessible text-based format is available online at https://support.unicheck.com/hc/en-us. Alternative formats are available upon request, at no additional charge. |
| (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 | All support content at https://support.unicheck.com/hc/en-us is available. Product support is available through standard non-TTY telephone and email. A ticket system for web requests is also available. |
Give us a feedback at accessibility@unicheck.com in user experience with Unicheck and get a thank you gift for your time.