VPAT – Voluntary Product Accessibility Template

This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate EvaluationKITs’ conformance with the WCAG 2.0 Standards, level AA.

Name of Product: EvaluationKIT
Date Updated: 10/01/2017

Principle 1: Perceivable

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

Guideline 1.1 Text Alternatives

 

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Criteria Supporting Features Remarks and explanations
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A) Supports The EvaluationKIT product provides alternative text for all relevant non-­text elements such as form elements, images, charts, etc.
Guideline 1.2 Time-based Media

 

Provide alternatives for time-based media.

Criteria Supporting Features Remarks and explanations
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A) Supports The EvaluationKIT product does not provide Prerecorded media.
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Supports The EvaluationKIT product does not provide Prerecorded media.
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Supports The EvaluationKIT product does not provide Prerecorded media.
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Supports The EvaluationKIT product does not provide Prerecorded media.
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Supports The EvaluationKIT product does not provide Prerecorded media.
Guideline 1.3 Adaptable

 

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Criteria Supporting Features Remarks and explanations
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Supports The EvaluationKIT product uses standard HTML markup for headings, forms, links, buttons, tables, lists, and other elements. HTML markup or ARIA and/or descriptive text is used to group the controls and the relationships between them.
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Supports The EvaluationKIT product works to ensure to keep all content in a meaningful order within the DOM. Grid or list data is presented as a standard HTML list or table elements. All modals provide aria-live alerts to give the control focus.
1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) Supports The EvaluationKIT product does not use sensory characteristics on content.
Guideline 1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
Criteria Supporting Features Remarks and explanations
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) Supports The EvaluationKIT product does not use color only for distinguishing a visual element.
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A) Supports The EvaluationKIT product does not automatically play audio.
1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA) Supports The EvaluationKIT product has a high contrast ratio by default. The use of customized account settings for header colors and logo image could alter the accessibility of the EvaluationKIT product. The EvaluationKIT product offers support with setup and recommendations to meet these guidelines.
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Supports All content in the EvaluationKIT product can be resized by the device browser.
1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA) Supports The EvaluationKIT product does not use images of text.

Principle 2: Operable

User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible

 

Make all functionality available from a keyboard.

Criteria Supporting Features Remarks and explanations
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. (Level A) Supports The EvaluationKIT product works to ensure that all components can be used through a keyboard interface.
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A) Supports The EvaluationKIT product works to ensure that all components can be used through a keyboard interface.
Guideline 2.2 Enough Time

 

Provide users enough time to read and use content.

Criteria Supporting Features Remarks and explanations
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) Supports All time sensitive content, such as survey start and end dates or intructor reporting, can have their deadlines adjusted by administrators.
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A) Supports The EvaluationKIT product has no areas utilizing blinking or scrolling information. Areas that auto-update, such as page postbacks, dashboard content, or modal alerts will provide aria-live alerts.
Guideline 2.3 Seizures

 

Do not design content in a way that is known to cause seizures.

Criteria Supporting Features Remarks and explanations
2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A) Supports The EvaluationKIT product does not use flashing content or media.
Guideline 2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
Criteria Supporting Features Remarks and explanations
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) Supports The EvaluationKIT product offers a “skip to content” link at the top of all pages, descriptive headings, ARIA landmarks, and HTML5 sections.
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A) Supports The EvaluationKIT product has descriptive and hierachical page tiles to represent the path of current navigation.
2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Supports The EvaluationKIT product works to ensure that the tab index of all web pages and controls are intuitive.
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Supports The EvaluationKIT product works to ensure all link text are meaningful.
2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Supports The EvaluationKIT product offers breadcrumb and main navigation on every page.
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) Supports The EvaluationKIT product works to ensure all Headings and labels are meaningful.
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Supports The EvaluationKIT product works to ensure that the current focus element is intunitive and visible on the page.

 

Principle 3: Understandable

Information and the operation of user interface must be understandable.

Guideline 3.1 Readable
Make text content readable and understandable.
Criteria Supporting Features Remarks and explanations
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) Supports The default language (“en”) is set on the HTML tag of all pages in the EvaluationKIT product.
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Supports, with exceptions The EvaluationKIT product displays context in default language. The use of other languages in surveys could alter the accessibility of the EvaluationKIT product. The EvaluationKIT product offers support with setup and recommendations to meet these guidelines.
Guideline 3.2 Predictable
Make Web pages appear and operate in predictable ways.
Criteria Supporting Features Remarks and explanations
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Supports The EvaluationKIT product works to not trigger context changes when items are focused. Although a few administrative search filter components trigger modals with further context and focus.
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Supports The EvaluationKIT product does not use the changing of input fields for initiating context changes.
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Supports The EvaluationKIT product has a consistent navigation across the site.
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Supports The EvaluationKIT product works to ensure that controls work consistently across the site.
Guideline 3.3 Input Assistance
Help users avoid and correct mistakes.
Criteria Supporting Features Remarks and explanations
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Supports The EvaluationKIT product uses automatic error alerts or summary above the form.
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Supports The EvaluationKIT product uses standard HTML or ARIA markup to associate descritive labels for all input fields or action buttons.
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Supports The EvaluationKIT product informs the user of any possible corections in a logical and intuitive manner.
3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA) Supports Users are presented with a modal confirmation before a modify or delete user-controllable data.

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria Supporting Features Remarks and explanations
4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Supports The EvaluationKIT product works to ensure that all markup is valid. The use of invalid markup in surveys could alter the accessibility of the EvaluationKIT product. The EvaluationKIT product offers support with setup and recommendations to meet these guidelines.
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) Supports The EvaluationKIT product works to ensure that elements are understandable to assistive technologies and screen readers with logical HTML markup and ARIA attributes.

Section 508 of the Rehabilitation Act

Name of Product: EvaluationKIT
Date Updated: 10/01/2017

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 The EvaluationKIT product works to ensure that all components can be used through a keyboard interface.
(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 EvaluationKIT product developer. Supports The EvaluationKIT product does not disable device browser 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 EvaluationKIT product works to ensure that the current focus element is intunitive and visible on the page.
(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 The EvaluationKIT product uses default browser features.
(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 The EvaluationKIT product uses visual only icons to some headers or button text.
(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 The EvaluationKIT product uses default browser features.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports The EvaluationKIT product uses default browser features.
(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 The EvaluationKIT product does not provide animation.
(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 The EvaluationKIT product does not use color only for distinguishing 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 use of customized account settings for header colors and logo image could alter the accessibility of the EvaluationKIT product. The EvaluationKIT product offers support with setup and recommendations to meet these guidelines.
(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 The EvaluationKIT product does not use flashing or blinking text, objects, or 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 The EvaluationKIT product works to use standard HTML markup for forms and action buttons. HTML markup or ARIA and/or descriptive text is used to group the controls and the relationships between them. The EvaluationKIT product works well with screen readers such as JAWS or NVDA.
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 Logo images in the EvaluationKIT product are non-relevant have no alt-text.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports The EvaluationKIT product does not offer multimedia presentations.
(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 The EvaluationKIT product does not use color only for distinguishing a visual element.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports The EvaluationKIT product does not required associated style sheet to be readable.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports The EvaluationKIT product 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 The EvaluationKIT product does not use server-side image maps.
(g) Row and column headers shall be identified for data tables. Supports The EvaluationKIT product uses standard HTML tables and headers for all grids of data.
(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 The EvaluationKIT product does not use data tables that have two or more logical levels of row or column headers.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports The EvaluationKIT product does not use frames. The EvaluationKIT product uses iframes in a small portion of the administration interface, with title attributes applied.
(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 The EvaluationKIT product 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 The EvaluationKIT product is a text based interface.
(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 EvaluationKIT product uses some dynamic content and advanced user interface controls that are developed with Ajax, HTML, JavaScript, and related technologies. HTML WAI-ARIA attributes help to make these controls or actions identifiable to screen readers.
(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 EvaluationKIT product does not use an applet, plug-in or other plugin application. Adobe Pdf is required for some reporting features and the EvaluationKIT product offers support with setup and recommendations to meet these guidelines.
(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 The EvaluationKIT product 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 The EvaluationKIT product has a “skip to content” link at the top of every page that will bypass all site and course navigation. The EvaluationKIT product also uses semantic HTML5 elements such as <nav>, <header> 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 Students are notified when elements are timed, and instructors can grant students additional time on timed elements on an as-needed, individual basis.
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 The EvaluationKIT product strives to work well with screen readers such as JAWS or NVDA
(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 The EvaluationKIT product uses default browser features.
(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 The EvaluationKIT product does does not require user 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 shall be provided. Supports The EvaluationKIT product does not use audio.
(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 The EvaluationKIT product does not require speech for operation or information retrieval.
(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. The EvaluationKIT product does not require fine motor control or simultaneous actions.
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 The EvaluationKIT product offers an accessible HTML, text-based format support system once authenticated. Other specific formats may require an 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 End users have access to this document and support features.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports The EvaluationKIT product offers an accessible HTML, text-based format support system once authenticated.