TidyUp Accessibility and Usability Information

Last evaluated: Feb 19, 2026

Get help

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

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

Additional resources

• TidyUp Overview, UW-Madison (Learn@UW KnowledgeBase document)

Evaluation results

Section 1: Home page, including “Files, Folders, Canvas Content” 

Overview of the page

Figure 1

Figure 1 caption: The home page consists of three tabs: “Files, Folders and Canvas Content.”

Barrier: Screen reader barrier

Figure 2

Figure 2 issue: In the “Canvas Content” tab, a user is meant to filter files by whether they are “Published,” “In Modules” or “Has Content.” When listening with a screen reader, it is announced to the user that they are using buttons, but it isn’t clear what the buttons do, nor is it announced that the user will manipulate table results by selecting a button. (The screenreader announces “Published, button, group” and “Not published, button, group.”)  A sighted user would see that the buttons are being used as a filter for the page, but when listening with a screen reader, it creates a barrier to understanding. 

Expected behavior: I would expect some announcement, perhaps a landmark, that I am interacting with filters that will manipulate the results that appear in the table.

This barrier primarily relates to the following accessibility guidelines:

• Web content appears and operates in predictable ways. (WCAG 3.2)

• Forewarn users if their context will change based on their input (3.2.2)

Barrier: Magnification barrier

Figure 3

Figure 3 issue: By 200% magnification, a user is required to use horizontal scroll to see all of the contents. When navigating by keyboard at 200%, the keyboard focus indicator goes off screen.

This barrier primarily relates to the following accessibility guidelines:

• Resize without assistive technology up to 200 percent without loss of content or functionality. (1.4.4)

• Everything can be done with a keyboard (2.1.1)

Barrier: Keyboard focus color contrast barrier

Figure 4

Figure 4 issue: When navigating by keyboard, the focus indicator does not meet contrast standards for WCAG 2.1 AA at the filters “All” and “Empty.”

This barrier primarily relates to the following accessibility guidelines:

• Everything can be done with a keyboard (2.1.1)

• Provide sufficient contrast between content and its background (1.4.3)

Barrier: Directional language 

Figure 5

Figure 5 issue: Directional language, such as “all files are shown below,” or “fields to the right,” creates barriers for screen reader users and users who magnify their screen. When listening to a page, fields noted as “to the right” create confusion. Hearing that files are “below,” doesn’t give good context to someone listening to a page. Also, when magnifying a page, content sometimes reflows such that what was once “to the right” can become “above” or “below,” for example.

Expected behavior: I’d expect that content would be referenced by its heading or landmark, not by its position on the page. For example,  “Files are listed in the table named ‘File information.’

This barrier primarily relates to the following accessibility guidelines:

• Describe controls by name, not just by appearance or location. (1.3.3)

Barrier: Table missing heading or caption

Figure 6

Figure 6 issue: Tables don’t have captions. There are identified table headers, which are helpful, but a heading or a caption for a table makes it easier to find when using a screen reader and easier to refer to.

This barrier primarily relates to the following accessibility guidelines:

• Provide descriptive headings and labels (2.4.6)

• Read about table captions and summaries from W3C. A caption for a table goes above the header row and serves as a table heading, allowing a screen reader user to navigate the page.  

Section 2: Pop-up dialogue

Overview of the pop-up dialogue

Figure 7

Figure 7 caption: The tester was asked to review the pop-up dialogue and found no barriers. 

Section 3: On-hover content within table

Barrier: preview image hidden from screen reader

Figure 8

Figure 8 issue: The text in the on-hover element is read as the screen reader moves through the table. However, the preview of the image is hidden from the screen reader. It would be helpful if the alt text for the preview image could be read, to give the user listening to the preview the same access as sighted users. The image is not decorative; it is instead a useful preview. 

Expected behavior: Since a file name might not help a user remember what file they are looking at, a small visual depiction helps the sighted user remember. As a screen reader user, I would expect to be able to achieve the same memory support sighted users are given by having the image alt text read to me, to help remember what the file is.

This barrier primarily relates to the following accessibility guidelines:

• Provide text alternatives for any non-text content (1.1.1)