What is a Web Access review?

The following process takes place at a Web Access review:

  1. The product/system/application owner and developers (people who work on the project) meet with the Web Accessibility team.
  2. The screen reader user connects her laptop to a projector and opens the project that is the subject of the review.
  3. The screen reader user reads through the first few items/pages using a screen reader and points out any initial issues.
  4. Following this initial run-through, the screen reader user will often attempt to complete tasks typically performed by users (such as filling out a form or finding specific pages), to determine if there are any accessibility blockers.
  5. Based on these findings, the Web Accessibility team will help determine the most critical accessibility errors found (if any), and provide recommendations for implementing fixes.

Clinic Priorities

  • Campuswide systems, applications, and web-based products will receive priority for available review slots.
  • Other campus websites should use Siteimprove and the DIY Accessibility Checklist, and follow the Website Owner Responsibilties as outlined on the Disability Access & Compliance website. 
    • The Web Access team may be able to hold reviews for other campus websites on a limited basis, depending on availability. 

For more information, please see the Request a Web Access Review page. 

Open Reviews benefit everyone!

Our Web Access reviews are typically "open," which means that in addition to the product/system/application owner and developers, other campus members who have subscribed to our Web Access mailing list are invited to attend.

Open reviews allow other campus teams to:

  1. Get an introduction to accessibility and why it’s important
  2. See a screen reader demo in person
  3. Learn accessibility best practices from other developers