Website Navigation for Blind Users: NavAccess Case Study — Concise Study Guide

Purpose of the case study

Hillen and Evers examined the difficulties blind users face when navigating websites and developed NavAccess, a prototype intended to make navigation more effective, efficient, and pleasant. A key motivation was that many earlier solutions improved access to a single page, while this project aimed to support navigation across an entire website. Source: [Working With Children and Adolescents: The Case of Claudia](material:124)

How NavAccess worked

NavAccess used a server-based agent to crawl pages within a website, follow internal links, and collect information about links and their destinations. The prototype design drew on prior studies, the User Agent Accessibility Guidelines (UAAG) 1.0, and the Web Content Accessibility Guidelines (WCAG) 1.0. Source: [Working With Children and Adolescents: The Case of Claudia](material:124)

Three focus challenges

• Providing guidance: helping users understand the current page, the wider site, and possible actions without forcing them to listen through large amounts of irrelevant content.
• Empowering users: supporting strategies blind users already use effectively, such as identifying landmarks and narrowing large sets of links.
• Reducing cognitive load: avoiding designs that overload attention or require users to manage multiple interfaces or excessive audio information.

Source: [Working With Children and Adolescents: The Case of Claudia](material:124)

Main findings from the evaluation

The researchers found that a separate or dual navigation interface was confusing for participants. Blind users generally preferred to work one page at a time rather than building a full mental model of the site as a whole. Audio preview cues delivered as sounds were also distracting because users were already relying on the auditory channel for screen-reader speech.

At the same time, several peripheral functions were seen as helpful when implemented well, especially main link identification, preview information, and context extraction. Source: [Working With Children and Adolescents: The Case of Claudia](material:124)

Design implications

• Support navigation step by step, matching how blind users actually find their way.
• Integrate helpful features into the main browsing interface instead of creating a separate mode.
• Provide optional summary information about the page and site, including what can be done on a page and the steps required.
• Offer preview information about link targets so users can judge whether a path is worth following.
• Help users filter and reduce long link lists, for example through search, duplicate removal, and visited/unvisited distinctions.

Source: [Working With Children and Adolescents: The Case of Claudia](material:124)

Key takeaway

The case study shows that accessibility design should not assume blind users need the same kind of broad site overview that helps sighted users. Instead, effective tools should strengthen users’ existing navigation strategies, reduce unnecessary mental effort, and deliver well-timed support inside the normal browsing experience. Source: [Working With Children and Adolescents: The Case of Claudia](material:124)