Skip to main content
CollegeSource Support

u.direct 4.2.1 VPAT

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

VPAT Updated

u.direct Version: 4.2.1

Date: October 23, 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.

 

 

Text Only View

Supports

All controls within the Text Only View are accessible using only a keyboard.

Standard View

Supports with Exceptions

 

  • Some buttons in u.direct are currently not implemented to be used with a keyboard alone.
  • IE & Chrome-Cannot use Up/Down Arrow key to select action from the list on the Manage Plans page.
  • Cannot use keyboard to select the Degree Program when adding a new plan.
  • Cannot use keyboard to access sub-trees in the degree program table when adding new plan or roadmap.
  • Cannot tab to Previous/Next buttons when performing a roadmap search, comments, roadmap publication requests, or plan approval request.
  • Cannot use keyboard to sort any row or column in the Notifications table.
  • DARwin/udirect-Cannot use keyboard to sort any column in the "My Advisees" table.

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

Supports The Text Only View does not disrupt or disable activated accessibility features of the products.
Standard View
Supports with Exceptions
  • When High Contrast Mode is On, all input fields in the student search page are hidden (FF only).
  • When High Contrast Mode is On, all input fields in the Login page are hidden (FF only).

View Accessibility Roadmap for Status and Timeline  

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 u.direct provides visual identification by clearly displaying 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 All meanings assigned to images remain 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

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.

Text Only View & Standard View

Not Applicable

u.direct has no 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 desired.

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

u.direct 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 & Standard View

Supports

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

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

Text Only View & Standard View

Not Applicable

Multimedia presentations are not utilized within u.direct.

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

Color is not exclusively utilized to convey information.

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

 

  • Some buttons in u.direct are currently not implemented to be used with styles turned off.
  • Cannot use keyboard to select the Degree Program when adding a new plan.
  • Cannot use keyboard to access sub-trees in the degree program table when adding new plan or roadmap.
  • Cannot tab to Previous/Next buttons when performing a roadmap search, comments, roadmap publication requests, or plan approval request.

View Accessibility Roadmap for Status and Timeline  

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

Text Only View & Standard View

Not Applicable

u.direct does not utilize 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.

Text Only View & Standard View

Not Applicable

u.direct does not utilize server-side image maps.

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

Text Only View & Standard View

Supports

Row and column headers are provided for all data tables.

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

Supports

All data tables have associations between data cells and header cells.

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

Text Only View & Standard View

Not Applicable

u.direct does not utilize 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.

Text Only View & Standard View

Supports

All pages within u.direct 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.

Supports with Exceptions

u.direct 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:

  • Total numbers of comments, plan approval requests, and roadmap publication requests do not show in the table headers for their notifications.
  • Does not provide the Installation Verification when user clicks on Help under Settings.

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 to 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

Supports

u.direct has the ability to export a PDF version of a roadmap or a plan. A link to Adobe Reader is located at the bottom of every page.

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

No areas within u.direct require a response within a certain time.

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

 

  • Screen reader does not read the description for all check boxes on the Comment page.
  • Screen reader does not read all clickable links inside the degree program table.
  • Screen reader does not appear to recognize the sort option in the Notifications table.
  • Screen reader cannot read all text and image in the Help window.
  • DARwin/udirect-Screen reader does not recognize the sort icon in any column in the "My Advisees" table.
  • DARwin/udirect-Screen reader does not read the email link or declared plan link in "My Advisees" page.
  • Screen reader does not recognize the sort button in any column in the View All Roadmaps table.

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

Supports Supports Assistive Technology for the blind or visually impaired.
Standard View
Supports with Exceptions
  • Screen reader does not read the description for all check boxes on the Comment page.
  • Screen reader does not read all clickable links inside the degree program table.
  • Screen reader does not appear to recognize the sort option in the Notifications table.
  • Screen reader cannot read all text and image in the Help window.
  • DARwin/udirect-Screen reader does not recognize the sort icon in any column in the "My Advisees" table.
  • DARwin/udirect-Screen reader does not read the email link or declared plan link in "My Advisees" page.
  • Screen reader does not recognize the sort button in any column in the View All Roadmaps table.

View Accessibility Roadmap for Status and Timeline  

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

u.direct 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

u.direct 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

u.direct 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 Does not require fine motor control or simultaneous actions.
Standard View
Supports with Exceptions

Standard View has drag and drop capabilities when building a roadmap or a plan. While there are methods of "manually" building a roadmap or plan, our goal is to find a more keyboard friendly alternative to drag and drop.

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.

 

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

 

 

 

 

 

 

  • Was this article helpful?