u.direct 4.2.2 VPAT

(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

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

Supports with Exceptions

• Some buttons in u.direct are currently not implemented to be used with a keyboard alone.
• Trees in u.direct are inaccessible via keyboard.
• When performing the Roadmaps search, keyboard cannot be used to access the Previous & Next buttons.
• The Previous and Next buttons on the Notifications page are inaccessible via keyboard.
• Rows and columns in the table on the Notifications page cannot be sorted via keyboard.
• Columns on the Advisees page cannot be sorted via keyboard.
• Rows on the Advisees page cannot be selected via keyboard to view a plan.
• The End Year field on the Roadmap cannot be edited via keyboard.
• The Request Plan Approval buttons is inaccessible via keyboard.
• The Remove All Courses button cannot be used with the keyboard.
  
  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.

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.

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.

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.

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

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.

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.

Supports

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

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.

Supports

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

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

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

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

Supports with Exceptions

Some buttons in u.direct are not currently implemented to be used with styles turned off.

View Accessibility Roadmap for Status and Timeline  

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

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.

Not Applicable

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

Supports

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

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

Not Applicable

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

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:

• Remove Roadmap association - HTTP status 404 error.
• TextOnlyView/Available Roadmaps - The labels for each column do not line up properly.
• TextOnlyView Roadmap - The start date has additional values compared to the Standard view.
• Text Only View - Synch view overlaps Adobe and Copyright message.
• Text Only View - No option to edit End Year & End Term.
• IE & Chrome Text Only View - Rows and columns in the Available Roadmaps are are inaccessible via keyboard.

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.

Supports

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

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

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

Supports

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

Not Applicable

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 visually impaired.

Supports with Exceptions

• Screen reader cannot read the Sort button in each column on the Notifications page.
• Screen reader cannot read the Sort button in each column on the Advisees page.
• Screen Reader cannot read the Sort button in each column on the View All Roadmaps page.

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.

• Screen reader does not appear to recognize the sort option in the Notifications table.
• Screen reader does not recognize the Sort button in any column in the "My Advisees" table.

• Screen reader does not recognize the Sort button in any column in the View All Roadmaps table.

• Screen reader reads the Reply/Edit/Delete buttons as "visited link" instead of the actual button name.
• Screen reader does not read the popup message for Delete/Copy/Rename Plan.
• Screen reader reads the Reply/Edit/Delete buttons as "visited link" instead of the actual button name.

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.

Supports

u.direct does not currently use audio components, so alternative 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.

Supports

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

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.

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  

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

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.