CalState S4 Accessibility Conformance Report

Revised Section 508 Edition

VPAT® Version 2.2 — March 2019

Product Description: A web-based application built on the Drupal CMS-framework that stores partnership data, tracks student placement data, and provides exports of that data.

Contact Information: Contact us

Evaluation Methods

Standards
§ Revised Section 508 standards – the U.S. Federal accessibility standard, published by the U.S. Access Board in the Federal Register on January 18, 2017
§ Corrections to the ICT Final Rule – a correction to the Revised Section 508 standards, published by the US Access Board in the Federal Register on January 22, 2018
§ Web Content Accessibility Guidelines 2.0 or WCAG 2.0 (ISO/IEC 40500), at http://www.w3.org/TR/2008/REC-WCAG20-20081211/

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.
  • Partially Supports: 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.
  • Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.

Report Information: [below table]

 

 

<-- OLD REPORT; NEW REPORT IN PROGRESS -->

Section 1194.22 Web-based Internet information and applications

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 All non-text elements are provided with textual equivalents, and web authors are given tools to provide alternate text as well.

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

Not Applicable The project does not include any multimedia presentation.

(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 Elements like status messages that convey information with color are accompanied with images or text that indicate the context.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports All information is semantically correct and "flows" naturally without stylesheets.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not applicable The project 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.

Not applicable The project does not use or condone the use of image maps

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

Supports All tables are rendered through a common API which provides for correct table headers.

(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 All tables are rendered through a common API which provides for correct table header scoping where appropriate.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Not applicable The project 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 The project does not use any animation techniques which cause screen flicker.

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

Not applicable The project uses only text or images with appropriate alternate content, so a text-only alternative is not necessary.

(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 JavaScript within the project exists merely to enhance user experience in certain cases and is not required to access content.

(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 The project does not use, nor condone, the use of applets.

(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 All forms in the project are rendered through a common system which ensures appropriate form labels and attributes are set, including appropriately marked "required field" indicators.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports A skip to content link is available for both non-sighted as well as sighted keyboard-only users.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports The project does not include any feature which requires a timed response.

Section 1194.31 Functional Performance Criteria

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 project supports the use of web standards and best practices to ensure the full project is accessible to the blind or visually impaired.

(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 visual layout and design of the project ensures that it will work well for users of assistive technology that enlare the print or entire layout of the site.

(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 There is no information in the project which includes audio.

(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 There is no information in the project which includes 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 There is no operation in the project which requires use speech.

(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 There is no operation which requires fine motor controls, and all objects which can be manipulated are accessible using expected keyboard functions like tab order.

Section 1194.41 Information, documentation, and support

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 All documentation is provided within the project or on the support site on standards-complient pages with readable text accompanied by videos with subtitles as well as full transcripts.

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

Not applicable Because the project adheres to web standards and best practices, there are no additional accessibility or compatability features.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Not applicable Because this is an open-source project that is non-staffed, there is no support service provided except for contextual help within the project itself and an associated support community.