Translating scroll-driven emotional gravity to a screen-reader navigable experience

Enabling screen-reader users to engage with a unique and highly visual digital art piece, while maintaining the integrity of the original work.

Role

UX Design (Solution Design, Prototyping, Technical Documentation)

Team

Myself, 2 User Researchers, 1 Designer

Timeline & Status

Apr 2025 - May 2025, 1.5 months, delivered

Overview

An Incalculable Loss is a significant piece of artistic journalism published by The New York Times that marks the first 100,000 American deaths resulting from COVID-19. Our client, Cooper Hewitt Smithsonian Design Museum is planning to include the piece in its upcoming collection of digital archives, and wants to ensure the experience is digitally accessible, particularly for blind or visually-impaired visitors.

I evaluated the accessibility of the existing piece, then designed, prototyped and documented specifications for an accessible, technically feasible framing experience to improve screen-reader compatibility for the piece.

Brief

How can we enable screen-reader users to engage with a unique piece of artistic journalism, while maintaining the integrity of the original work?

Cooper Hewitt asked our team to design a framing experience for the digital media piece, An Incalculable Loss, that

1
Provided an accessible experience for screen-reader users
2
Did not alter the code of the original piece
3
Translated the visual aspects of the piece to an auditory experience that honors the design choices made by the original authors.
Artwork

What themes should be maintained across both visual and screen-reader accessed experiences?

After discussing with our client, referencing the artwork's significance statement and experiencing the artwork ourselves, we determined the most important aspects of the artwork to make accessible to screen-reader users were

1
Highlighting the humanity of the individuals who lost their lives to COVID.
2
Endless-scroll sensation that emphasizes the significant number of lives lost to COVID.
3
Accurate, linear timeline progression of the article.
Persona

Who are we designing for, and what's different for screen-reader users?

The Incalculable Loss piece is set to be displayed in an online gallery, primarily accessed by art students based in New York City. For those art students who are blind or visually-impaired, our team did some further research. We learned

Behaviors vary, but the tool stays the same

According to research from WebAIM and University of Maryland, some users scan a page using headlines, some move through element-by-element. The one unifying feature is that, all navigation happens on the keyboard. The key to quality design will be providing clear options early in the page structure to support keyboard-enabled exploration and autonomy.

Users' website experience is almost entirely dependent on code structure

Screen reader technology relies on html structure and ARIA labels to navigate web pages. This meant that if we could not alter the code of the piece itself, we would need to introduce new "framing experience" code and design the structure of the code itself, to ensure the highest quality user experience.

Process

Investigating the code structure to understand what's possible

Because the quality of our solution would depend on the quality of the implementation, I investigated the code structure to understand how a screen reader would navigate the piece as built and what was parsable from the existing code structure.

What I found #1

Key mismatch between code structure and emotional experience of the piece

Code Structure
Visual Experience
What I found #2

Code is well-structured for parsing and reimagination

Narrative Blocks

Each overarching section is labeled as “g-slide” . Each white box occurs throughout every other “g-slide” section. This pattern of a section with a narrative box, then a section without, repeats throughout the entire piece.
Magnified Narrative Block
Inspected Narrative Block

Person Blocks

Each person has a class label as “g-orbit” as well as an associated death date label. This allows the person’s death date to be associated with the small white counter.
Magnified Person Highlight
Inspected Person Highlight

Death Count

The date and death counter is tracked and recorded with two labels, “g-day” tracks the number of days that has passed and “g-count” tracks the number of deaths. These are updated by the scroll position.
Magnified Death Count
Inspected Death Count
Early Concept

Provide a persistent panel, operable by keyboard, that gives users a linear storytelling of the piece populated by extracted and re-organized data.

Early Concept Design of Framing Experience

Following a design-thinking approach, I conceptualized our minimum viable product that would satisfy the functional needs of our users - meeting WCAG's principle guidelines of being perceivable, operable, understandable, and robust.

This solution relies on the extraction of each of the three elements (filled and empty narrative boxes, person blocks, and the death count) to populate a linear script that persists on a right side panel. This panel would operates as our frame.

Feasability Check

Is this something that could really work?

Yes! Because the code's class structure is clean and predictable, a developer could write a python script using python library Beautiful Soup to extract elements from the existing webpage and populate our screen-reader script that appears inline on the right hand of the screen.

Solution

A linear storytelling that puts individuals front and center.

Gif of Solution Prototype

Standardized interaction pattern gives users autonomy to "skim" or "doom scroll"

In our panel, we provide the users with two different options for how they can navigate each section. They can either jump ahead, mimicing a large fast scroll or step through each individual's story, mimicing a slow small scroll.

Navigation Options Highlighted with Focus State in Solution
An Aside

Why keep the narration panel visible on the right, when the text is already on-screen?

Not every person who uses a screen reader is blind. Following from research conducted at the University of Washington, it's essential not to ignore the visual channel of perception when designing for low-vision users.

Handoff & Technical Documentation

Desiging the UX for after we're gone.

To ensure our client had everything they needed to implement our accessible solution, I built thoroughly annotated wireframes, a diagram highlighting static vs dynamic content, as well as a video-walk through of our prototyped solution.

Snapshot of dynamic vs static content highlighting
Keyboard navigation annotations
Instructions for how to navigate prototype
Takeways

This might be my new favorite project.

I loved the attention to detail, creative problem solving and technical consideration required to meet this project brief. I found it incredibley energizing to work through problems of this complexity and hope to do more work like it in the future.