Get help

• Contact the DoIT Help Desk for general assistance. Reach the Help Desk by phone at 608.264.4357, email at help@doit.wisc.edu or visit their KnowledgeBase.

• For accessibility or usability assistance for NameCoach, please contact learnuwsupport@wisc.edu.

Additional resources

• NameCoach Overview, UW-Madison (KnowledgeBase document)

Accessibility and usability barriers 

The following information is provided to help people with disabilities know what potential barriers may exist and to help people who support them. This is not a comprehensive list of barriers. Our team evaluates common user flows, looking for patterns of barriers. We do not evaluate the entire application.

Keyboard navigation barriers may limit access for people with motor disabilities.

Some keyboard focus indicators do not have strong contrast, which makes it difficult to follow the keyboard navigation. Additionally, elements are included in the tabbing order which are not selectable, which is a confusing experience when using keyboard navigation. Refer to Figure 1 for an example:

Figure 1 caption: The bar that lets the user know that the app is synching receives keyboard focus (and doesn’t meet contrast standards), but the element is not clickable.

Some contrast barriers exist, creating barriers for people with low vision or who are color blind.

Some buttons, selected menu items, and keyboard focus indicators lack strong contrast, making it difficult to read. Refer to Figure 3:

Figure 3 caption: Keyboard focus on some elements creates color contrast that does not meet WCAG standards.

​​Magnification barriers create difficulties perceiving information for some users, such as people with low vision

When magnified at and above 250%, the user must scroll horizontally to reach all content. Refer to Figure 4:

Figure 4 caption: When magnified, horizontal scroll is required, instead of enabling a reflow that avoids horizontal scrolling.

Skipped headings create screen reader barriers that may create challenges for some users, such as people who are low vision or blind or have a reading disability.

Headings are skipped on several pages, which can create a confusing user experience. Refer to Figure 5 for an example.

Figure 5 heading: In this example, the heading level 2 (h2) is followed by a heading level 4 (h4), rather than having headings that proceed sequentially. 

Lack of status updates make search function difficult for users navigating via screen reader, such as people who are low vision or blind 

When searching in the class roster in the Namecoach Canvas integration, a screen reader user is never given a status update when a search is loading or when it has finished loading. The user must also manually clear the name from the search field in order to remove the filter on the roster, as the button to clear the field is skipped in the navigation order.

Screen reader announcements may disrupt name recording for users navigating via screen reader, such as people who are low vision or blind

Some screen readers may continue announcing while a user is trying to record their name. These users may need to pause the screen reader to use the record feature.