On this page

All pages




The purpose of the Voluntary Product Accessibility Template, or VPAT, is to assist buyers in making preliminary assessments regarding the availability of commercial “Electronic and Information Technology” products and services with features that support accessibility.  

The first table of the Template provides a summary view of the Section 508 Standards.  The subsequent tables provide more detailed views of each subsection.  There are three columns in each table.  Column one of the Summary Table describes the subsections of subparts B and C of the Standards.  The second column describes the supporting features of the product or refers you to the corresponding detailed table, e.g., “equivalent facilitation."  The third column contains any additional remarks and explanations regarding the product.  In the subsequent tables, the first column contains the lettered paragraphs of the subsections.  The second column describes the supporting features of the product with regard to that paragraph.  The third column contains any additional remarks and explanations regarding the product.


Date: February 9, 2017
Name of Product: Totara 9 – Student Login

Summary Table

VPAT

Voluntary Product Accessibility Template®

Criteria

Supporting Features

Remarks and explanations

Section 1194.22 Web-based Internet Information and Applications

 Overall is 508 compliant in most areas.

Few issues that need to be addressed. see comments in the 1194.22 section.




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 with exceptions

Review ALT items to make sure there is a description for non-decorative items.

Some pages need to add any <object>Alternative text content</object> for objects.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Supports


(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.

Supports


(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


(g) Row and column headers shall be identified for data tables.

Supports with exceptions

Some of the table pages to be changed to distinguish the table header and rows

(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.

Supports


(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).

Supports


(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 with exceptions

Add labels to some form controls

Add a name to the form control

Add label and title elements where necessary

(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.

Supports with exceptions

Some of the page META REFRESH times are not zero. These should be adjusted to zero.

Change the META refresh time to 15 seconds or more, or zero (since all users are affected equally)

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.