VPAT

Atomic Jolt Voluntary Product Accessibility Template (VPAT)

This Voluntary Product Accessibility Template, or VPAT® Version 2.1, is a tool that administrators and decision-makers can use to evaluate Atomic Jolt’s conformance with the accessibility standards under Section 508 of the Rehabilitation Act and the Act WCAG 2.1 AA Standards.

Product: Atomic Search, Atomic Assessments, Atomic Polls, Atomic Discussions, Atomic Curriculum Tools

Date: January 2020

Contact: info@atomicjolt.com

We have evaluated our products and found them to be substantially conformant with Level A and Level AA of the Web Content Accessibility Guidelines version 2.1. While not fully conformant, conformance issues that pose a significant barrier for users with disabilities have been addressed in the sample evaluated.

A sample of the frequently used aspects of our products were evaluated in both Student and Instructor roles. This sample included Atomic Search, Atomic Assessments, Atomic Curriculum Tools, Atomic Polls, and Atomic Discussions.

We cannot verify the conformance of content outside the scope of the representative sample, or content changed after Jan 7, 2020. However, we promise to continually work to maintain conformance.

Note: This product operates inside of the Canvas LMS, we do not control the accessibility of their software. You may refer to the Canvas VPAT for information on their level of conformance.

Note: Atomic Assessments includes software from Learnosity. As a Learnosity partner, Atomic Jolt provides feedback and coordinates with Learnosity to resolve any accessibility issues. Please see Learnosity's accessibility page for more information on how they approach accessibility.

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.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.

Atomic Jolt Web Content Accessibility Guidelines (WCAG 2.1) Checklist

WCAG 2.1 Guidelines

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Criteria Conformance Level Remarks and Explanations
1.1 Text Alternatives: Provide text alternatives for any non-text content. Supports Elements have appropriate text alternatives.
1.2 Time-based Media: Provide alternatives for time-based media. Not Applicable Does not have time-based media
1.3 Adaptable: Create content that can be presented and navigated in different ways. Supports All content is presented in a logical way and can be navigated easily.
1.3.4 Orientation: Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. Supports Content does not rely on screen orientation.
1.3.5 Identify Input Purpose: The purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
Supports Input fields follow purpose.
1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background. Supports Sufficient color contrast is used throughout.
1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
- Vertical scrolling content at a width equivalent to 320 CSS pixels;
-Horizontal scrolling content at a height equivalent to 256 CSS pixels;
Except for parts of the content which require two-dimensional layout for usage or meaning.
Supports Content reflows to accommodate extreme sizes.
1.4.11 Non-Text Contrast: The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
- User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
- Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Supports Sufficient color contrast is used throughout.
1.4.12 Text Spacing: In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
- Line height (line spacing) to at least 1.5 times the font size;
- Spacing following paragraphs to at least 2 times the font size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
Supports Text changes do not effect the functionality of our apps
1.4.13 Content on Hover or Focus: Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
- Dismissable A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
Supports Hover content is easily dismissed and works according to the guidlines.

Principle 2: Operable

User interface components and navigation must be operable.

Criteria Conformance Level Remarks and Explanations
2.1 Keyboard Accessible: Make all functionality available from a keyboard. Supports All content is keyboard accessible
2.1.4 Character Key Shortcuts: If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
- Turn off A mechanism is available to turn the shortcut off;
- Remap A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc).
- Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus.
Supports Keyboard shortcuts are only ever used on focused elements.
2.2 Enough Time: Provide users enough time to read and use content. Supports No time-based content is involved
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 Supports multiple ways of filtering content
2.5.1 Pointer Gestures: All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. Supports No multipoint or path-based gestures are used.
2.5.2 Pointer Cancellation: For functionality that can be operated using a single pointer, at least one of the following is true:
- No Down-Event The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
- Up Reversal The up-event reverses any outcome of the preceding down-event;
- Essential Completing the function on the down-event is essential.
Supports Most functions do not use down-events to trigger and those that do are easily reversed or canceled.
2.5.3 Label in Name: For user interface components with labels that include text or images of text, the name contains the text that is presented visually. Supports Names on inputs contain the text that's presented visually.
2.5.4 Motion Actuation: components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface The motion is used to operate functionality through an accessibility supported interface;
- Essential The motion is essential for the function and doing so would invalidate the activity.
Supports No motion actuation is used.

Principle 3: Understandable

Information and the operation of user interface must be understandable.

Criteria Conformance Level Remarks and Explanations
3.1 Readable: Make text content readable and understandable. Supports Text is written in plain english
3.2 Predictable: Make web pages appear and operate in predictable ways. Supports Navigation is consistent
3.3 Input Assistance: Help users avoid and correct mistakes. Supports  

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 Conformance Level Remarks and Explanations
4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies. Supports  
4.1.3 Status Messages: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. Supports  

Section 508 of the Rehabilitation Act

Section 508

SECTION 1194.21 SOFTWARE APPLICATIONS AND OPERATING SYSTEMS – DETAIL

Criteria Conformance Level 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  
(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  
(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 When focus is overridden, we provide 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 Browser and labels
(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  
(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 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  
(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  
(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. Not Applicable  
(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  

SECTION 1194.22 WEB-BASED INTERNET INFORMATION AND APPLICATIONS – DETAIL

Criteria Conformance Level 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  
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not Applicable  
(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  
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports  
(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable  
(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  
(g) Row and column headers shall be identified for data tables. Supports  
(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  
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports  
(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  
(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  
(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  
(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  
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports  
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable  

SECTION 1194.31 FUNCTIONAL PERFORMANCE CRITERIA – DETAIL

Criteria Conformance Level 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  
(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  
(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  
(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  
(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  
(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  

SECTION 1194.41 INFORMATION, DOCUMENTATION AND SUPPORT – DETAIL

Criteria Conformance Level 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  

Back to Top