Skip to main content
CollegeSource Support

uAchieve Schedule Builder 4.4 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

    uAchieve Schedule Builder Version: 4.4

    Date: January 13, 2017

    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 508 Standards for details on Section 1194.21)

    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.

    Text-Only View

    Supports with Exceptions

    The following areas are inaccessible via keyboard:

    • The Search Results page
    • The Course sections

    View Accessibility Roadmap for Status and Timeline

    Standard View
    Supports with Exceptions

    The following areas are inaccessible via keyboard:

    • Sort Column on the Result page
    • Course sections
    • Course Title
    • Course Number

    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.

    Text-Only View & Standard View

    Supports Schedule Builder does not disrupt or disable the activated accessibility features of the products.

    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.

    Text-Only View & Standard View

    Supports Schedule Builder provides a well-defined on-screen indicator of the current focus.

    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.

    Text-Only View & Standard View

    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.

    Text-Only View & Standard View

    Supports The meaning assigned to those images remains consistent throughout the application.

    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.

    Text-Only View & Standard View

    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.

    Text-Only View & Standard View

    Supports with Exceptions

    Application does not override user-selected contrast and color selections or other individual display attributes except in the following case:

    • General Preference is hidden when Windows High Contrast is on.

    View Accessibility Roadmap for Status and Timeline

    h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

    Text-Only View & Standard View

    Not Applicable Schedule Builder does not use 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.

    Text-Only View & Standard View

    Supports

    Color coding is 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.

    Text-Only View
    Not Applicable Since stylesheets are not utilized within the Text-Only View, the ability for a user to switch stylesheets does not apply.
    Standard View

    Supports

    Standard View currently allows users to switch from a "default" stylesheet to a "high contrast" stylesheet. Schools have full control over the styling of the "default" and "high contrast" styles, and can even add additional style options, if needed.

    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.

    Text-Only View & Standard View

    Not Applicable

    Schedule Builder contains no flashing or blinking text.

    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.

    Text-Only View & Standard View

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

    Text-Only View

    Supports

    Alt text or a text equivalent is provided for every non-text element.

    Standard View

    Supports with Exceptions

    On the My Schedule/Select All Courses buttons, NVDA does not read the label on each button, but instead only mentions the button.

    Schedule Builder does not let the screen reader user know that an alert has appeared on the page indicating that changes have not yet been saved.

    View Accessibility Roadmap for Status and Timeline

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

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to 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.

    Text-Only View & Standard View

    Supports

    All of the information conveyed with color is also available without color.

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

    Text-Only View
    Supports Text-Only View does not utilize a style sheet.
    Standard View

    Supports

    Standard View is readable without a style sheet.

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

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to 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.

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to Schedule Builder.

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

    Text-Only View
    Supports Row columns and headers are provided for all data tables.
    Standard View

    Supports with Exceptions

    • NVDA does not read headers on the Sections tab.
    • Columns in the Find Courses table cannot be sorted.

    View Accessibility Roadmap for Status and Timeline

    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.

    Text-Only View & Standard View

    Not Applicable

    Schedule Builder has no data tables with two or more levels.

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

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to 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.

    Text-Only View & Standard View

    Supports

    All pages within Schedule Builder have been designed not to 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.

    Text-Only View & Standard View

    Supports with Exceptions

    Schedule Builder has a Text-Only View of the entire application. Users can access everything that can be accessed in the Standard View with the following exceptions:

    • On the My Schedule/Select All Courses buttons, NVDA does not read the label on each button, but instead only mentions the button.
    • Clicking on Help under Settings opens a blank page instead of re-directing to the Installation Verification page.

    View Accessibility Roadmap for Status and Timeline  

    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.

    Text-Only View & Standard View

    Supports

    Any information provided by scripting languages is accessible 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).

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to 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.

    Text-Only View & Standard View
    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.

    Text-Only View & Standard View

    Supports

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

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

    Text-Only View & Standard View

    Not Applicable

    Criterion does not apply to 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.



     

    Text-Only View

    Supports

    Supports Assistive Technology for the blind or visually impaired.

    Standard View
    Supports with Exceptions

    The screen reader cannot read the following:

    • Sort image in the Find Courses Table.
    • Column header for Course Number.
    • Plus "+" image as the Add button.
    • The actual day in the Busy Times table.
    • All of the days in the Schedule table.
    • The correct time in the Time Preferences.
    • Create or Clear button in Time Block Preferences.
    • The label for Busy Times.
    • The Row1\Column on the Schedules\Search Results page.
    • Lock All Courses.
    • Unlock All Courses.
    • Delete All Courses.
    • Schedule preview.
    • Search button in My Current Schedule.
    • The dash sign "-"
    • Heading labels in each row under Sections.

    A Form Label is missing from the following:

    • Drop-down box for year/term selection.
    • Selection Action box and checkbox.
    • Checkbox for Hide Conflict Courses.
    • Radio buttons for Sections, Time/Day, and input box for Busy Times.
    • The drop-down box and radio buttons are missing in the auto-generate Schedules/Set Preferences area.
    • General Preferences.
    • Time Between Courses range and Time Block.
    • Radio buttons in Find Courses/Advanced Options.
    • Busy Times in the Description box.
    • Radio Buttons for selecting the time.
    • The check box for enrolling around sections and full sections.

    Additional issues include the following:

    • Sections and Busy Times have empty Table Header.
    • The input field is missing Form Label from Find Courses area.
    • Time Block, courses pairs, and NOT pairs have Empty Buttons.
    • Time Between Courses range has Empty Link.
    • Preferences/Time Block has Empty Table Header.
    • Year Term Setup and Course Indexing have Empty Table Header in Schedule Admin.
    • Busy Times has Empty Table Header.
    • Find Course page is missing Title.
    • Close button in the pop-up window for Help for course search has broken ARIA.
    • Help for the Application Functions has empty Table Header.
    • Home page image on the installation verification page has Empty link.
    • Total Course Preferences page has a link without label.

    View Accessibility Roadmap for Status and Timeline

    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.

    Text-Only View & Standard View

    Supports Supports Assistive Technology for the 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.

    Text-Only View & Standard View

    Supports

    Schedule Builder does not currently use audio components, so other means of operation and information retrieval are 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.

    Text-Only View & Standard View

    Supports

    Schedule Builder does not currently use audio components, so other means of operation and information retrieval are provided.

    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.

    Text-Only View & Standard View

    Supports

    Schedule Builder does not require user speech, so other means of operation and information retrieval are provided.

    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.

    Text-Only View 

    Supports

    The Text-Only view is keyboard accessible.

    Standard View
    Supports with Exceptions

    The following areas are inaccessible via keyboard:

    • The Search Result page.
    • Course sections, Course Title, and Course Number.

    View Accessibility Roadmap for Status and Timeline

     

    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 Text-Only View and Standard 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.

    • Was this article helpful?