V2: Screen Reader Usability Testing

[bbertucc]

Test Question

How can we improve our User Experience for Screen reader users?

Data

• diverse_PDF_key.csv: URLs and expected outcomes
• diverse_PDF-upload.csv: File that you can upload to Equalify

Process

Add as a comment on this thread any issues and feedback that pops up as you follow these steps:

1. Login at https://app-staging.equalify.uic.edu/
2. Create a new Audit named "Screen Reader Usability Testing" with the date also in the title
3. Enable email notifications with your email
4. Add two URLs to the scan.
5. Upload the upload CSV to the scan.
6. Save and run audit.
7. View Audit.

[Rogue-Git-Dev]

Does selecting the Upload.csv file just upload all of the URLs or is that something different? I fail to understand why to select two URLs to upload and upload the Upload.csv file which contains more URLs than just two.

[Rogue-Git-Dev]

Also, after selecting the Upload.csv file and thus population of the table of URLs, must the type be changed from HTML to PDF or shall the type be left as is? There are more than two URLs in the table. Must all but two be unticked? Finally, the Save and Run button does nothing after the file was selected. Must the Add URLs button be activated first?

[cskchao]

• No column header label in URL table col 1. This can make the unlabeled checkboxes appear ambiguous.
• Several button labels are read twice. (NVDA + FF)
• Success/error messages written to the top line are not automatically announced while using NVDA + FF
• Audit appears to suggest no email notifications when email notification switch from builder screen is set to on

[bbertucc]

@cskchao can you checkout the login process: https://app-staging.equalify.uic.edu/audits

[cskchao]

@cskchao can you checkout the login process: https://app-staging.equalify.uic.edu/audits

Seemingly nothing out of the ordinary since last time. Screen reader focus lands on the h1 reading "Audits"