GMU: Can assistive technology compensate for poor web accessibility?

PlatformResearch
RoleUX Researcher — Research Proposal, User Testing, Interviews, Quantitative & Qualitative Analysis
YearAug 2022 - Dec 2022
CollaboratorsMary Nichols (literature review, website redesign, surveys)

Capstone Project at the Visual Attention and Cognition Lab, Department of Psychology — part of a 2-year M.A. in Human Factors and Applied Cognition.

A capstone research project at George Mason University's Visual Attention and Cognition Lab, using Tobii eye-tracking to prove that WCAG principles are essential — not optional — for creating websites usable by everyone. When 97.4% of top websites fail accessibility guidelines, the burden falls on assistive technologies that were never designed to compensate.

Overview

If 97.4% of websites fail accessibility, can assistive technology bridge the gap?

In 2021, WebAIM analyzed the top 1,000,000 most visited websites and found that 97.4% of homepages contained features that don't conform to the Web Content Accessibility Guidelines (WCAG). This places a significant burden on assistive technologies — tools primarily designed to work with accessible websites, not compensate for inaccessible ones.

This eye-tracking study was the capstone of my two-year M.A. in Human Factors and Applied Cognition at George Mason University, where I applied human factors psychology as a cognitive foundation for interaction design, usability engineering, and accessible web architecture. Eye-tracking was the right instrument for the question: it surfaces where attention actually goes, moment to moment, in a way self-reported surveys and interviews can't.

This study investigated two research questions:

1. If a website adheres to WCAG accessibility guidelines, is costly assistive technology (such as magnification software) necessary?

2. If a website doesn't adhere to WCAG accessibility guidelines, can assistive technology compensate for the lack of accessibility?

Most Common WCAG Failures (WebAIM, 2021)
Table of the most common WCAG accessibility failures across the top 1 million homepages in 2021, led by low contrast text at 86.4% and missing alt text at 60.6%
Key Findings

The Conclusion

Assistive technology is unnecessary for accessible websites — but cannot compensate for inaccessible ones.

Participants were successful when using the accessible website, without needing assistive technology. However, when navigating an inaccessible website, they faced significant challenges and required assistive technology.

While tools like magnification software can aid users with macular degeneration, they cannot fully compensate for poor website accessibility. Accessibility guidelines need to be treated as a baseline, not an optional add-on, if the industry wants to actually support low-vision users.

Background

Vision disability is the fifth most common disability in the U.S.

Severe vision loss presents problems with reading, navigating, using assistive technology, and using the internet. Low vision is most commonly caused by macular degeneration, cataracts, diabetic retinopathy, and glaucoma. U.S. adults with a disability are 3× less likely to use the internet (Pew Research Center, 2017), are over 3× less likely to be employed (BLS, 2022), and report higher levels of social isolation compared to their abled counterparts.

Percentage of U.S. Adults by Functional Disability Type
Bar chart of U.S. adults by functional disability type: mobility 13.7%, cognition 10.8%, independent living 6.8%, hearing 5.9%, vision 4.6%, self-care 3.7%
Pain Points of Assistive Technology

Most assistive technologies are expensive and hard to use for browsing websites, which could affect low-vision users' employment status and social integration. Screen magnifiers, a commonly used assistive technology, have three significant problems:

  1. They impede screens globally
  2. They disrupt spatial orientation
  3. They lead to excessive scrolling

Challenge

Running a rigorous eye-tracking study with real constraints.

  • Limited budget to recruit real low-vision participants
  • Strict timeline with just one week to conduct the experiment
  • The topic is broad — hard to propose focused, defensible research
  • Had to set up the Tobii eye-tracking system from scratch with no prior lab infrastructure

Method

Simulating macular degeneration — the most common cause of low vision.

To simplify this experiment, I selected the most common cause of low vision, macular degeneration, and simulated its symptoms — a central scotoma with blurred vision — using the Silktide Disability Simulator Chrome extension.

I employed a within-subjects experimental design, where each participant completed the same tasks on both website types to control for extraneous variables. To mitigate order effects, two participants initially completed tasks on the accessible website, while one participant began with the inaccessible website.

Participants

Three graduate students with normal or corrected-to-normal vision took part in the study.

Tools
  • Tobii eye tracker — tracking eye movements on both websites to observe behavioral differences visually
  • Silktide Chrome extension — simulating a central scotoma and blurred vision attached to mouse movements
  • Zoom magnification software — positioned at the top of the screen to prevent screen occlusion, magnifying text at the mouse's location
Tobii Eye Tracker Lab Setup
Tobii eye tracker mounted beneath a monitor in the lab, with the eye-tracking software actively exporting a recording

Websites Tested

One accessible, one intentionally inaccessible — identical information, different WCAG compliance.

I selected a website crafted from top to bottom with WCAG web accessibility principles (the New South Wales Government Website) and created a redesigned mockup website identical in information but with no accessibility principles.

Three Key Visual Differences

1. Homepage — The accessible site had sufficient contrast, readable font and font size, and was developed from WCAG guidelines. The inaccessible version used insufficient contrast, cursive fonts, and all-caps text.

2. Dropdown Menus — The accessible site used multicolumn/multirow dropdowns with hover-state color changes and highlighted tab headers. The inaccessible site used single-column dropdowns with no visual feedback on hover or selection.

3. Column Layout — The accessible site had even, single-column layouts easy to read under a magnification lens. The inaccessible site had uneven/unnecessary columns that were difficult to read using magnification.

Column Layout: Accessible (left) vs. Inaccessible (right)
Accessible website column layout — even, single-column, readable under magnification
Inaccessible website column layout — uneven columns, difficult to read under magnification

User Testing

Think Aloud method with eye-tracking — observing real struggle in the lab.

Participants arrived at the laboratory and verbally agreed to be recorded. They calibrated their pupils with the Tobii eye tracker, which compiled screen recordings of their eye-tracking fixation locations on the websites.

Participants were shown the Silktide disability simulator (scotoma attached to mouse movements) and the Zoom magnifier at the top of the screen. They were instructed to navigate and read as they normally would, using the Think Aloud Method.

Tasks
  1. Find a place to get swabbed for COVID-19
  2. Look up regulations about COVID-19 in the area
  3. Find support for people with a disability in COVID-19

I took notes as participants completed the tasks, recording their thoughts, reactions, and behaviors. Below, each red dot is a fixation — a point where the eye stops to process information, sized by how long the gaze lingered — and the connecting lines are saccades, the rapid jumps between one fixation and the next.

Eye-Tracking Gaze Plot — COVID-19 Dropdown Navigation
Eye-tracking gaze plot over the NSW Government website with the COVID-19 dropdown open — red fixation dots and saccade lines trace where the participant looked

Quantitative Results

Participants completed tasks 6 minutes faster on the accessible website.

Task Completion Time

Participants averaged 6 minutes faster on the accessible website across all three information-finding tasks — though with only three participants, a paired t-test found the gap fell short of statistical significance (p > .05).

Mean Time to Complete Tasks (Minutes)
Table showing mean time to complete tasks in minutes — the accessible website totaled 2:06 across three tasks, the inaccessible website totaled 8:17
Task Completion Rates
  • 3/3 participants completed all 3 tasks on the accessible website
  • 2/3 participants failed to complete at least one task on the inaccessible website
System Usability Scale (SUS)
  • Industry average: 68 (according to usability.gov)
  • Accessible website scored 88.33 — well above the industry average
  • Inaccessible website scored 64.17 — falling below the industry average
SUS Scores: Accessible vs. Inaccessible
Bar chart comparing System Usability Scale scores — accessible website scored 88.33, inaccessible website scored 64.17, against an industry average of 68

The data confirms it: assistive technology alone can't close the gap an inaccessible site creates.

Qualitative Results

What participants actually said — and what their eyes revealed.

We coded the session notes and audio against the eye-tracking recordings using the HyperResearch qualitative analysis tool, tagging recurring behaviors and reactions across both website conditions.

On the Accessible Website

Participants reported finding the site "pretty easy" and "clearer." They navigated without needing the magnification reader, using their peripheral vision to read around the simulated scotoma. The dropdown "isn't flying around everywhere" — multicolumn layout allowed scanning without losing context.

On the Inaccessible Website

Participants struggled significantly. "I'm using the shadow to see." When they tried the magnifier, it did not help — "I'm not sure what this is so I would definitely need the magnification for this part. Which really doesn't help considering that it's still really small." The dropdown "was the same color as the background," making navigation nearly impossible.

Eye-tracking data showed larger, more erratic fixation patterns on the inaccessible site — participants' eyes were searching, not reading. The bigger the red fixation dots, the longer a participant stared at something they couldn't understand.

Qualitative Feedback — Word Cloud
Word cloud of participant feedback sized by frequency — largest terms are 'Difficult to see' and 'Dropdown difficulty,' followed by 'Did not use mag reader,' 'Magnification reader difficulty,' and 'Easy to see'
Reading Behavior — Accessible Website (with Magnification)
Reading Behavior — Inaccessible Website (with Magnification)
Dropdown Behavior — Accessible Website (with Magnification)
Dropdown Behavior — Inaccessible Website (with Magnification)

Synthesis

The accessible site validated three behaviors; the inaccessible site exposed three fixes.

Accessible Website
  • All participants reported they thought they completed every task
  • All participants reported the site was easy to read — scotoma off to the side, no magnification reader needed
  • Dropdowns with multicolumn/multirow format worked significantly better than single-column
Inaccessible Website

1. Contrast is the primary barrier. WCAG requires a minimum 4.5:1 contrast ratio for normal text — a bar the inaccessible site fell well short of. Contrast directly affects the ability to read and gather information, accounts for the 6-minute average task time difference, and is one of the easiest accessibility issues to fix.

2. Dropdown format matters for low vision. Vision issues, especially scotomas, hinder the effectiveness of single-column dropdowns. Multicolumn/multirow is substantially more usable.

3. Small graphics and fonts fail even with magnification. Not even magnification readers can clarify undersized elements — the problem is in the design, not the tool.

Future Directions

Expanding the study to validate findings at scale.

  • Expand the study to real low-vision users — replace the simulator with actual visually disabled participants for more accurate insights
  • Expand to other types of assistive technologies such as screen readers
  • Get 5+ participants (Jakob Nielsen recommends qualitative testing with 5 users)
  • Replace the SUS questionnaire with a dedicated accessibility instrument (SUS measures overall usability rather than accessibility, and requires 12+ users for validity)
  • Switch to Eyelink eye tracker from Tobii — supports heat map generation and area-of-interest analysis via Weblink software

Learnings

Research rigor meets real-world constraints.

Participant Demographics

The usability testing participants were solely graduate students in their twenties. This skewed the data, since younger participants tend to be more comfortable with technology and more receptive to adopting new tools. A more representative study would switch from a visual disability simulator to actual visually disabled participants across age groups.

Project Management

A one-week testing window left no room to explore a topic this broad — only to narrow it fast. I cut scope down to the two most defensible research questions and moved straight into execution, adjusting the plan as constraints surfaced rather than following one fixed from day one.

Recognition

The capstone was one piece of a broader research practice.

Alongside this capstone, I conducted ethnographic research into how people actually use assistive technology day to day — a separate empirical project examining the same accessibility questions from outside the lab. Across both, R, SPSS, and mixed-method frameworks turned behavioral data like the task-completion times and SUS scores above into evidence, not anecdote.

That research practice traveled outside the program, too. In November 2022, I won the Usabilathon 2022 — sponsored by HelloFresh — a UX audit design marathon focused on HelloFresh's mobile app.

Further Reading

Want to go deeper into the research?

Read the full research report for the complete methodology, literature review, and data behind this study. Prefer slides? The eye-tracking and low vision presentation walks through the same findings deck-style. The study's boards and supporting artifacts are also collected in the Figma file.

I also studied accessibility in a different context: a usability comparison of the Amazon Alexa and Google Nest smart-home apps, a separate UXR study from the same program.

Related Work