What is it about?

This paper is about how people with different levels of eyesight (blind, low-vision, and sighted) work together in a knowledge workplace. It looks at the problems blind and low-vision workers face when using charts, spreadsheets, and documents that are designed only for people who can see. It also explains how coworkers communicate, learn about each other's needs, and find creative ways to fix these problems so that everyone can do their jobs effectively.

Featured Image

Why is it important?

Many workplaces care more about getting things done fast than making sure everyone can participate. This leaves blind and low-vision workers struggling, stressing over whether their work looks messy, or having to do extra steps just to read a simple file. This topic is important because it highlights a major hidden struggle in the office. It shows that if we change how we create and share information from the very beginning, we can make workplaces fairer, more welcoming, and much less stressful for everyone.

Perspectives

We often think accessibility as a one-way phenomenon where a workplace simply hands a specialized tool to a disabled employee and assumes the problem is solved. However, looking at this analytically shows it is actually a two-way street that relies heavily on teamwork and communication. For example, sighted coworkers take active steps to change how they work. They might stop using confusing layouts like merged cells, start adding clear text headings, or proactively describe charts. This requires ongoing conversations. Blind workers must feel safe sharing what they need without fear of looking less productive, and sighted workers must be willing to ask, "Does this format work for you?" and adjust their work based on the answer.

Yichun Zhao
University of Victoria

Read the Original

This page is a summary of: "If We Had the Information That We Need to Interpret the World Around Us, We Wouldn't Be Disabled:" Barriers and Opportunities in Information Work among Blind and Sighted Colleagues, June 2026, ACM (Association for Computing Machinery),
DOI: 10.1145/3808045.3808061.
You can read the full text:

Read

Contributors

The following have contributed to this page