Skip to main content
CollegeSource Support

Schedule Builder 4.2 VPAT

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

VPAT Updated

Schedule Builder Version: 4.2.0

Date: May 20, 2014

Contact: accessibility@collegesource.com

The terminology used in the second column is predefined and consistent across all tables in the VPAT. This terminology dictates the content of the third column:

Terminology used in "Supporting Features"

(second column) 

What this terminology means

How to complete "Remarks and Explanations"

(third column)

Supports Product FULLY meets the letter and intent of the Criteria List exactly what features of the product do meet the Criteria, and describe how they are used to support the Criteria

 

Supports with Exceptions

 

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

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

AND        

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

Supports through Equivalent Facilitation Product provides alternative methods to meet the intent of the Criteria 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 Product fully meets the letter and intent of the Criteria when used in conjunction with Compatible Assistive Technology List exactly what Comparative Assistive Technology is used with the product, and describe how it supports the Criteria
Does Not Support Product does not meet the letter or intent of the Criteria Describe exactly how the product does not support the Criteria
Not Applicable Criteria do not apply to the product Describe exactly why the Criteria is not applicable to the product

 

Not Applicable-Fundamental Alteration Exception Supplies

 

Criteria do not apply to the product due to the necessity of a fundamental alteration of the product

Describe exactly why the Criteria is not applicable to the product

AND 

List exactly what fundamental alterations could be made to the product to make it support the Criteria

Summary Table

 


 

Summary Table

VPAT™

Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems    
Section 1194.22 Web-based Internet Information and Applications    
Section 1194.23 Telecommunications Products N/A N/A
Section 1194.24 Video and Multimedia Products N/A N/A
Section 1194.25 Self-Contained, Closed Products N/A N/A
Section 1194.26 Desktop and Portable Computers N/A N/A
Section 1194.31 Functional Performance Criteria    
Section 1194.41 Information, Documentation and Support    

 

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

User cannot use the keyboard to navigate to either Schedule tab or Sections tab

Cannot use the keyboard to sort the column in the Find Courses page

View Accessibility Roadmap for Status and Timeline

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

Application does not disrupt or disable activated features that are identified as accessibility features, nor does it disrupt or disable activated 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

  • Screen reader cannot read the special characters in the Settings/Change Password
  • screen reader cannot read the sort image in the Find Courses Table
  • screen reader does not read the column header for Course Number
  • screen reader does not read the + image as Add button
  • screen does not read Create or Clear button when creating or clearing busy times
  • screen reader does not read the actual day in the Busy Times table, it just reads each letter in the table (M T W H F S S)
  • screen reader reads all the days in the schedule table except Sunday
  • screen reader reads the time incorrectly in the time preferences under the Time Between Courses Range
  • Time Block Preferences - screen reader does not read Create or Clear button
  • Time Block Preferences - need a label for the days of the week

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

All elements have alt-text to comply with Assistive Technology.

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

In Schedule Builder, user cannot use keyboard alone to check and uncheck the radio button.

View Accessibility Roadmap for Status and Timeline

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

Application does not override user selected contrast and color selections or other individual display attributes.

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

Criteria does not apply to u.direct and Schedule Builder.

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 used in conjunction with disabling features within this application and is therefore not the only means of conveying information.

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

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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

All elements that can be considered 'forms' within the application comply to the guidelines as stated.

 

Section 1194.22: Web-based Internet information and applications


(Refer to the 508 Standards for details on Section 1194.22)

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

Alt-text is provided for every non-text element.

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

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

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

Color is not utilized to convey information.

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

Supports

Text-Only view does not utilize a style sheet, but provides all information as the version that does utilize style sheets.

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

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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.

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

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

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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

My Schedule/Select All Courses - NVDA does not read the label on each button, it only mentions button

 

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.

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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

Text-only versions of forms provide the same functionality, elements, and information as the standard view of the web-based product.

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

Supports

"Skip Navigation Links" are provided as the first links on all text-only pages.

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

Not Applicable

Criteria does not apply to u.direct and Schedule Builder.

NOTE: The Board interprets paragraphs (a) through (k) of Section 1194.22 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

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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

Criteria does not apply to u.direct and Schedule Builder.

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

Support documentation is provided for both standard view and text-only view at no 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

Access to a description of accessibility and compatibility features is provided in both a print, Assistive Technology-friendly format or by telephone support at no additional 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.

 

To generate a PDF version of the Schedule Builder VPAT, click the "Export to PDF" option under the "Tools" drop-down menu on the top-right of this page:

 

 

 

 

 

 

  • Was this article helpful?