Skip to main content
CollegeSource Support

Dashboard 4.1.5 VPAT

 

This document is the Voluntary Product Accessibility Template (VPAT) for the Dashboard. For an overview of VPATs, view the Product VPATs page.

VPAT Updated

Dashboard Version: 4.1.5

Date: November 25, 2013

Contact: accessibility@collegesource.com

Overview

Supporting Features (Second Column of Evaluation Template)

Language

Description

Supports

Product FULLY meets the letter and intent of the Criteria

Supports with Exceptions

Product does not ENTIRELY meet the letter and intent of the Criteria, but does provide some level of access

Supports through Equivalent Facillitation

Product provides alternative methods to meet the intent of the Criteria

Does Not Support

Product does not meet the letter or intent of the Criteria

Not Applicable

The Criteria does not apply to the product.

Remarks & Explanations (Third column of Evaluation Template)

If second column states...

Then ...

Supports

List exactly what features of the product do meet and describe how they are used to support the criteria

Supports with Exceptions

List exactly what features of the product do meet and describe howthey are used to support the criteria

AND

List exactly what features of the product do not meet and describe how they fail to support the criteria

Supports through Equivalent Facilitation

List exactly what other methods exist in the product and describe how they are used to support the criteria.

Supports when combined with Compatible Assistive Technology

Use this language when you determine the product fully meets the letter and intent of the Criteria when used in conjunction with Compatible Assistive Technology. For Example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).

Does Not Support

Describe exactly how the product does not support the criteria.

Not Applicable

Describe exactly why the criteria is not applicable to the product.

Not Applicable - Fundamental Alteration Exception Supplies

Use this language when you determine a Fundamental Alteration to the product would be required to meet the Criteria (see Access Board standards for the definition of "fundamental alteration").

Section 1194.21: Software Applications and Operating Systems

 Refer to (http://www.access-board.gov/sec508/guide/1194.21.htm *) for details on the guidelines listed below.

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 Dashboard runs without issue completely from 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

The Dashboard does not disrupt or disable other products with industry standard accessibility 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 with Exceptions

The staff home page doesn't display clear focus once you are outside of the menu.

View Accessibility Roadmap for Status and Timeline  

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

Title text not showing for all toolbar and button options, specifically those on the staff home page.

View Accessibility Roadmap for Status and Timeline  

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

All meanings for images remain consistent throughout the Dashboard

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

Textual information is provided through the operation system functions for displaying text.

g) Applications shall not override user selected contrast and color
selections and other individual display attributes.

Supports

The user can set colors, contrast, and fonts as they wish without issue.

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

There isn't any animation in Self Service

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

Color coding is not used as the only means of conveying information on the Dashboard.

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.

Not-Applicable

Not applicable to Dashboard

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

Dashboard does not use flashing or blinking of any form

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

Assistive technology when used with dashboard allows the user to access all information without issue.

Section 1194.22: Web-based Internet information and applications

 Refer to (http://www.access-board.gov/sec508/g.../1194.22.htm\* (http://www.access-board.gov/sec508/guide/1194.22.htm*)) for details on the guidelines listed below.

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

Title text not showing for all toolbar and button options, specifically those on the staff home page.

View Accessibility Roadmap for Status and Timeline  

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

Not-Applicable

No multimedia presentations apply to Dashboard

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

Dashboard can convey all of it's information without the use of color.

 

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

Supports

Dashboard is readable without a style sheet.

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

Not-Applicable

Not applicable to Dashboard

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

Not applicable to Dashboard

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

Supports

Row and column headers display and work as expected

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

Markup is used to associate data cells and header cells for 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

Not-Applicable

Not applicable to Dashboard

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

Not applicable to Dashboard

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

A text only page would be provided if compliance cannot be accomplished in any other way.

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

Information provided by scripts are identified with functional text and are readable by assistive technology.

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

All applets present include a link that complies with 1194.21(a) through (l).

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.

Not Applicable

Not applicable to Dashboard.  No forms exist in Dashboard.

 

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

Does not Support

Dashboard does not have a link to skip repetitive navigation links.

View Accessibility Roadmap for Status and Timeline  

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

Not-Applicable

Timed Responses are not required in Dashboard

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.

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.

Supports Assistive Technology for the blind or vision-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

Supports Assistive Technology for visually impaired.

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

Product does not currently use audio components; support for Assistive Technology for the deaf or hard-of hearing is provided.

 

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.

Not-Applicable

Not applicable to Self Service

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.

Not-Applicable

Not applicable to Self Service

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.

Not-Applicable

Not applicable to Self Service

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

Documentation will be provided free of charge in whatever form is needed.

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

We will provide print or phone support at no charge

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

Supports

Support services accommodates the communication needs of end-users with disabilities

 

 

 

  • Was this article helpful?