Voluntary Product Accessibility Template (VPAT)

This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate the level to which knowbly™ conforms to the standards under Section 508 of the Rehabilitation Act and WCAG 2.0 AA.

Accessibility Conformance Report

VPAT Version 2.0 - January 2018

Name of Product: knowbly™

Date: April 2019

Applicable Standards/Guidelines: This report covers the degree of conformance for the following accessibility standard/guidelines:

  • Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017
  • Web Content Accessibility Guidelines 2.0 (Level A/AA) conformance is also documented herein.  

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.
  • Supports with exceptions: Some functionality of the product does not meet the criterion or does not apply.
  • Does not support: The majority of product functionality does not meet the criterion.
  • Not applicable: The criterion is not relevant to the product.

WCAG 2.0 Report

This table documents conformance of the knowbly authoring tool with WCAG 2.0

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. Supports Non-text media (e.g. images) allows for the inclusion of alt text and long descriptions.Time-based media (e.g., audio, video) include support for captions and/or the inclusion of a text alternative within the content itself.
1.2 Time-based Media: Provide alternatives for time-based media. Supports As noted above, knowbly™ provides for captions and text alternatives for time-based media such as audio and video.Additionally, there is support for including descriptive audio-alternatives (e.g. narration) for image-centric time-based media.
1.3 Adaptable: Create content that can be presented and navigated in different ways. Supports Through the use of semantic HTML and web "best practices", reading and navigation order is typically logical and intuitive.Additionally, the authoring tools allow for the inclusion of separate, alternative methods by which to present content.
1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background. Support with exceptions Default themes provide accessible color palettes and contrast ratios. Additionally, users are able to build their own themes/templates to adjust the color palette and contrast to their specific needs.As noted above, use of semantic HTML allows the user to leverage built-in capabilities within their chosen browser to resize text to make it more legible.

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. Support with exceptions Standard course content and some widget/interactive content is keyboard accessible.Development work to support keyboard accessibility across all interactive types is currently underway.
2.2 Enough Time: Provide users enough time to read and use content. Supports Timing and flow of content is at the author’s discretion.
2.3 Seizures: Do not design content in a way that is known to cause seizures. Support with exceptions Content does not flash. However, we do not limit the media content added to a course or widget, and so it is at the author’s discretion to include media content that does not conform.
2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are. Support with exceptions As noted above, the use of semantic HTML and web “best practices” ensure the content is navigable and understandable via mouse, touch, and keyboard.As with many things, however, much discretion is afforded the author and it is possible for the author to structure their content in a non-intuitive manner and/or not fully make use of the provided accessibility helper tools.

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 Content supports multiple languages but always has a specified language per web standards.
3.2 Predictable: Make web pages appear and operate in predictable ways. Supports Navigation is consistent across and predictable across published content pages and individual learning objects.
3.3 Input Assistance: Help users avoid and correct mistakes. Support with exceptions Important labels and instructions are not always accessible for widget/interactive content.

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. Support with exceptions ARIA attributes are sometimes not present, predominantly where widgets are concerned, and thus rely on semantic HTML to support assistive technologies such as screen readers.As noted above, work is underway and ongoing to provide additional accessibility support for widgets.

Section 508 of the Rehabilitation Act

Section 1194.21 software applications and operating systems - detail VPAT™

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 knowblyTM strives to ensure all content 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 knowblyTM does not interfere or override 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 knowblyTM.
(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, knowblyTM uses default browser focus styles. In cases where the author has elected to override those styles through custom design, knowblyTM strives to retain the distinctiveness of 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 knowblyTM uses icons to help depict the purpose of certain interface elements (e.g. arrow buttons for navigation back and forth in a media gallery).knowblyTM in its default state, as well as through the theming/template tools available to the author, provides a means by which such iconography can remain consistent throughout the content.Additionally, assistive technology readable labels (e.g. alt text) are 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. Supports Authors are enabled to provide as many forms of alternative media/content as are necessary.
(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 knowblyTM 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. Support with exceptions The interface of knowblyTM content using default themes has been styled with CSS to comply with Section 508's contrast and color settings. However, authors may choose to alter the color/contrast theming of their content.
(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 knowblyTM 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. Not applicable knowblyTM does not generally make use of form-based content.In the case of interactives/widgets where input is required (e.g. a “fill in the blank” assessment), work is underway to provide for the requirements of assistive technologies.

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 Images and other non-text elements in knowblyTM content provide support for alt-text and long descriptions.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports 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 knowblyTM content does not use color alone to distinguish the importance of a visual element. However, an author can choose to override such provisions.
(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 knowblyTM with the associated style sheets disabled.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports knowblyTM 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 knowblyTM does not use server-side image maps.
(g) Row and column headers shall be identified for data tables. Supports Data tables, a native element type provided by knowblyTM , are by default marked up with informative column and row headers. However, an author is given the freedom to adapt the table format and layout at their discretion.
(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 knowblyTM 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 Supports As with all navigable elements, knowblyTM strives to include meaningful default labels and identifiers.
(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 knowblyTM does not intentionally 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 knowblyTM is compliant with all provisions of this section, so a text-only version is unnecessary.However, an author can choose to supply text-only alternatives to any content authored in knowbly.
(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. Support with exceptions knowblyTM uses javascript, WAI-ARIA and semantic HTML5 techniques and “best practices” to provide feedback from interactive elements and to allow Assistive Technology such as screen readers to read and transmit information back to the user.As noted earlier in this document, work is underway and ongoing to ensure all interactives/widgets conform to these standards.
(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 knowblyTM 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 knowblyTM does not generally make use of form-based content.In the case of interactives/widgets where input is required (e.g. a “fill in the blank” assessment), work is underway to provide for the requirements of assistive technologies.
(o) A method shall be provided that permits users to skip repetitive navigation links. Does not support
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not applicable

Note to 1194.22: knowbly™ interprets items of this section as consistent with the Web Content Accessibility Guidelines 2.0 (WCAG 2.0) (December 8, 2008) published by the Web Accessibility Initiative of the World Wide Web Consortium: (a) 1.1, (b) 1.2, (c) 1.4, (d) 1.3 (g) 1.3, (l) 4.1, and (o) 2.4.

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. Support with exceptions knowblyTM strives to ensure content works well with screen readers.As noted earlier in this document, work is underway and ongoing to ensure all interactives/widgets conform to these standards.
(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 knowblyTM content supports screen magnification and zoom functionality via built-in browser capabilities.
(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 knowblyTM content does not require hearing for operation except in cases where audio tracks, either alone or as part of a video, are included. In such cases, provisions are made to include and support text-based alternatives.
(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 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 knowblyTM 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 knowblyTM 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 Product support text-based and interactive formats are available online at https://help.knowbly.com Alternative formats can be made available upon request.
(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://help.knowbly.com is available in text-based and interactive formats. Alternative formats can be made available upon request.

For any questions or further details regarding this VPAT™ attestation from Knowbly Learning Systems, Inc. please contact support@knowbly.com