Web Accessibility Report - Universal Robots Website

HCI 511: Accessibility Considerations

The first slide of the project's presentation, says web accessibility report, Universal Robots

Executive Summary

Universal Robots (UR) is a pioneer in collaborative robots, known for its user-friendly automation solutions. The company caters primarily to industrial automation companies. A comprehensive assessment uncovered many accessibility flaws, most notably regarding text alternatives, proper labeling, form accessibility, and their website structure. Methods to uncover these flaws includes W3C’s “Easy Checks”, a cognitive level test, automated evaluations (using WAVE and Google Lighthouse), and a personal screen reader (NVDA) experience. UR should prioritize offering thorough alt-text, descriptive labels, keyboard accessibility, and error identification to improve accessibility on their forms and website. Ensuring a smooth and accessible browsing experience for people with disabilities also requires improvements in the use of ARIA, color contrast, and general content readability.

Tasks

  • Audit: Conducted a website accessibility audit using industry standards
  • Analysis: Identified areas for improvement in content and design for better accessibility
  • Recommendations: Provided suggestions to enhance usability and compliance with accessibility guidelines
  • Documentation: Documented findings and suggested actionable steps for the design team

Introduction

Universal Robots (UR) is one of the global leaders in collaborative robots (cobots). In addition to their cobots, UR has developed some of the most advanced automation solutions available. BMW, along with other leading companies, has recognized UR for their user-friendly and flexible design, integrating them into production processes to improve efficiency and safety (BMW Group, 2013). Any further investigation into UR and their motivations as a company shows that they are committed to be reliable and innovative in both the automation and robotics field.

Universal Robots logo

https://www.mhi.org/members/75525

Services

We recruited three visually impaired participants through personal networks, ensuring they were at least 18 years old. The study was conducted virtually using Zoom, with participants performing tasks related to browsing, adding items to their cart, checking out, and reviewing orders. Data was collected through recordings, notes, and affinity diagrams to identify patterns and themes.

Audience

UR appears to target enterprises in the industrial automation field, looking to optimize their production without investing too heavily into robotics. While you might find large factories using UR’s cobots, a few applications use smaller scale cobots in an office setting. It also seems that UR is interested in emerging applications as the desire for automation grows into new fields.

Methods and Tools

For this assessment, I reviewed both the Universal Robots homepage and the product page for their UR10e cobot, see the Appendix for current screenshots. I have done my assessment in Google Chrome as of October 2023. For the accessibility evaluation, I followed and used the guidelines and tools below:

W3C "Easy Checks"

The first list I used comes from W3C with “Easy Checks” – A First Review of Web Accessibility. These are preliminary checks that all websites should consider before publishing their website.

Readability Level (Cognitive Level Test)

All text assessment for this method involved the usage of Readable. This method involves copying and pasting text found on UR’s website to make sure it is at an 8th grade reading level or below.

Automated Evaluations (WAVE and Google Lighthouse)

For the automated tools, I used the WAVE Google Chrome extension and Google’s built-in tool, Lighthouse, to evaluate UR’s website against the POUR guidelines.

ARIA Assessment

I used Axe DevTools to identify if the website’s usage of ARIA is correct in addition to WAVE and Google Lighthouse. However, I also manually checked it using Google Chrome’s “View Source” functionality to view their code. I referenced Mozilla’s documentation on ARIA to ensure that their usage is correct and consistent with the standards.

Screen Reader Experience

To check how a screen reader functions on the UR website, I used the popular reader, NVDA. This is a personal experience rather than a true evaluation. By attempting to use their website with a screen reader, I can determine if a screen reader user would be able to access the website effectively.

Findings

The following section organizes discoveries according to the POUR guidelines (Perceivable, Operable, Understandable, Robust). This includes findings from the “Easy Checks” process, the ARIA assessment, readability level, and the automated evaluations.

Screen Reader Experience

While the website’s accuracy surprised me, there were still moments in which the screen reader seemingly ignored large sections of the webpages. The heading structure provided an easy way to get to major sections of information, but as a sighted user, I could see some sections ignored by the reader. Related to the ARIA errors, the “play” button over the videos came up quickly and only announced itself as “clickable button”. For someone who is not able to see what that button is for, you must take a risk to click a button that has no label, and you must trust the website is not taking advantage of you. On top of some small inconsistencies and mislabeling, there is work for UR to do. Overall, I believe someone who is blind or has low vision would be able to navigate these webpages, but they may be concerned/confused.

Recommendations (Abbr.)

  • Ensure all images have unique, descriptive alt-text.
  • Provide accessible labels for all buttons and form fields.
  • Enable autocomplete on forms for common information (name, email).
  • Make drop-downs on the "Request a quote" form keyboard accessible.
  • Provide clear error messages and suggestions for form inputs.
  • Add captions and descriptive transcripts to videos.
  • Use a logical heading structure (avoid skipping heading levels).

  • Use a logical heading structure (avoid skipping heading levels).
  • Fix ARIA issues (e.g., search bar and "play" button).
  • Improve color contrast for links in the footer.
  • Avoid seizure-inducing visuals in video transitions.
  • Add an option to skip the navigation menu.
  • Use an 8th-grade reading level for website text.
  • Use the <abbr> tag for abbreviations.

References

  1. BMW Group. (2013, September 10). Innovative human-robot cooperation in BMW Group production. Retrieved from BMW Group Press: https://www.press.bmwgroup.com/global/article/detail/T0209722EN/innovative-human-robot-cooperation-in-bmw-group-production?language=en
  2. Universal Robots A/S. (2023, October). Retrieved from Universal Robots: https://www.universal-robots.com/
  3. Universal Robots A/S. (2023, October). UR10e. Retrieved from Universal Robots: https://www.universal-robots.com/products/ur10e/

Let's Connect

I'm quick to respond, get in touch for opportunities or to say hi!