Visual Communication for Low-Vision Information Access

When I magnify a chart enough to read one bar, the axis and legend can disappear from my view. I can see the bar, but I lose what it means.

I have albinism and low vision, and I use screen magnification every day. That gap between detail and context connects my research. Writing my doctoral symposium paper meant putting the connection into words.

My paper “Visual Communication for Low-Vision Information Access: From Personalized Highlights to AI Agents” (Sechayk, 2026) was accepted to the UIST 2026 Doctoral Symposium. 🎓 In November, I’ll present it in Detroit to a panel of senior researchers.

What is a doctoral symposium? PhD students present their dissertation plans to senior researchers and get feedback while there is still time to change them. Think of it as a friendly stress test for the research.

Seeing a fragment at a time

Magnification makes things bigger by showing only part of the screen at a time. That tradeoff matters when information is spread across a page.

In a lecture video, an instructor can mark a sentence outside my magnified view. In a chart, I can see the bar under my pointer while its axes and legend sit elsewhere. Sometimes I don’t even know what I missed.

Magnification shows only a fragment of the page. On the left, the whole page: a heading, a few lines of text, one highlighted sentence, a small bar chart, and its legend. A small purple frame marks the part of the page that fits in the magnified view. It covers only the middle of the sentence. An arrow leads to the right, where the magnified view shows that part much larger, with the words cut off at both edges. Text below it says that only part of the sentence fits, and everything else is out of view. The whole page My magnified view Only part of the sentence fits. Everything else is out of view. Magnification shows only a fragment of the page. At the top, the whole page: a heading, a few lines of text, one highlighted sentence, a small bar chart, and its legend. A small purple frame marks the part of the page that fits in the magnified view. It covers only the middle of the sentence. An arrow leads down to the magnified view, which shows that part much larger, with the words cut off at both edges. Text below it says that only part of the sentence fits, and everything else is out of view. The whole page My magnified view Only part of the sentence fits. Everything else is out of view.
Magnification makes what I'm reading big and clear, but only a piece of the sentence fits in view at once. The heading, chart, and legend around it are out of sight.

Using the vision we have

Many people with low vision prefer to use the vision they have. Speech, sound, and touch can also make visual information accessible, but they don’t directly support that way of seeing.

So what if we build on the vision people already use?

My research follows ability-based design: start with what a person can do, then shape the tool around their abilities. For me, that means working alongside tools such as magnification, allowing people to adjust the visual support, and designing with people with low vision. Their needs and strategies differ, and their vision can change with the situation.

Visual communication, in two directions

The thread that ties my projects together is visual communication in two directions. A tool can show me where to look with a highlight or bring missing context into my view. I can show a tool what I’m looking at by sharing my magnified view and where I point. What happens when both directions work together?

A four-column timeline of my research, read left to right. VeasyGuide (ASSETS 2025) highlights an instructor's mark on a lecture slide. On-Cursor Visual Context (CHI 2026) shows two chart interactions, Dynamic Context and Mini-map. Visual Context for AI (ongoing) shows a user pointing at a bar in a chart while an AI assistant answers with its value. Visual Communication with AI Agents (future) asks whether visual dialogue with AI builds independence or creates reliance, and whether AI should tell, highlight, guide, or show. Labels along the bottom read: how tools can communicate visually with low-vision users, how low-vision users communicate visually with AI, and how bidirectional visual communication impacts agency.
My research trajectory. It starts with tools that communicate visually to low-vision users, moves to low-vision users who communicate visually with AI, and heads toward visual communication in both directions.

From tools that show to tools that see

My dissertation follows this idea step by step. Each project taught me something, and each lesson shaped the next one.

VeasyGuide: a highlight is a message

In a lecture video, an instructor may point to a part of a slide without naming it. VeasyGuide (Sechayk et al., 2025) makes that action easier to find with a highlight that can appear before the action and with magnification that can follow it. My co-design partners helped decide how the highlight should look and behave. You can read how we designed VeasyGuide or try it in your browser.

Three panels of VeasyGuide. Panel a, the VeasyGuide player: a lecture slide titled Machine Learning, where a red bounding box with a translucent yellow fill highlights the phrase the instructor is marking, next to a hand-shaped pointer icon. Panel b, zoomed-in view: pressing the Z key shows a magnified view of the highlighted slide text. Panel c, personalization panels: settings for the fill color and opacity, border color and width, pointer shape and scale, filters named Invert, Thicker, and Thicker dark, and the highlight's shape and animation.
VeasyGuide marks an instructor's action with a personalized highlight and pointer icon (a), can zoom in to follow the action (b), and lets each learner tune how the highlight looks (c).

Takeaway: a highlight has to be findable, predictable, and adjustable to communicate anything. It should also leave the learner free to decide whether to follow it.

But a chart poses a different problem: the context I need is spread across axes, legends, and data points.

On-Cursor Visual Context: bring context into view

On-Cursor Visual Context (Sechayk et al., 2026) explores two ways to keep chart context available under magnification. Dynamic Context brings axes and legend information near the pointer, with a crosshair to help trace values. Mini-map keeps a small overview of the chart in view.

The crosshair came from a participant’s workaround: they used the edge of their docked magnifier as a ruler because the chart’s grid lines were too faint.

Top: an illustration of a person leaning close to a monitor to read a bar chart, next to an annotated bar chart titled Car Counts by Number of Gears, with callouts labeling its overview, legend, grid lines, and axes. Bottom: two monitors showing visual context interactions under screen magnification. On the left, Dynamic Context shows a magnified part of the chart with the Count axis values, the Transmission legend, the Number of Gears axis label, and a crosshair gathered in a compact area around the pointer. On the right, Mini-map shows a magnified part of the chart with a small overview of the whole chart in the corner and a dot marking where the pointer is.
The context a chart reader needs (top), and two ways to bring it into the magnified view (bottom): Dynamic Context gathers the axes, legend, and a crosshair around the pointer, and Mini-map keeps an overview of the whole chart in view.

Takeaway: context can move into the magnified view, and people’s workarounds can show us how. But a fixed display can’t answer the next question a reader has about the chart.

Visual context for AI: let the tool see what I see

What if an AI assistant could see where I’m looking in a chart? In my ongoing work, I’m exploring an assistant that receives the user’s magnified view and pointer location as context. That lets a person point and ask without first describing exactly where they are in the chart.

The next question: can the assistant answer in a way I can see? The user can show the assistant their visual context, but the assistant answers in words. It can tell me where to look, but it can’t show me. That brings me back to the problem VeasyGuide started with.

Next: both directions

I want to study an assistant that can also answer visually: highlight a region, guide my attention along a path, or adjust the view. Then the person and the tool could each show the other what they mean. I also want to explore this beyond charts, starting with information seeking on web pages and eventually extending to documents and the physical world.

Put together, the projects form one arc. VeasyGuide and On-Cursor Visual Context show that tools can communicate visually with people with low vision. The AI work turns this around, so people can communicate visually with their tools. The next step closes the loop.

Who decides where to look?

Should the tool move my view, highlight something and let me look, or just answer? The right response may depend on the person and the task.

Four kinds of help, and the person chooses between them. A circle in the center reads I choose. Four equally sized cards surround it, each connected to the circle by a line. Tell, answer in words, shown with a speech bubble. Highlight, mark a region, shown with a tinted, outlined box. Guide, point the way, shown with a dashed arrow. Adjust view, reframe the screen, shown with a small frame inside a larger one. Text below reads: the right response depends on the person and the moment. I choose Tell answer in words Highlight mark a region Guide point the way Adjust view reframe the screen The right response depends on the person and the moment. Four kinds of help, and the person chooses between them. A circle at the top reads I choose. Below it, four equally sized cards are stacked. Tell, answer in words, shown with a speech bubble. Highlight, mark a region, shown with a tinted, outlined box. Guide, point the way, shown with a dashed arrow. Adjust view, reframe the screen, shown with a small frame inside a larger one. Text below reads: the right response depends on the person and the moment. I choose Tell answer in words Highlight mark a region Guide point the way Adjust view reframe the screen The right response depends on the person and the moment.
Tell, highlight, guide, or adjust the view. These are different kinds of help, not a ranking, and the right one depends on the person and the moment.

More assistance is not always more access. Being able to look for myself is part of what I value. I don’t want a tool that sees for me. I want one that helps me see.

My dissertation asks how people with low vision and their tools can show each other what they mean, extending the sight we already use rather than replacing it. Through all of it, the person stays in control of what they see.

See you in Detroit

At the symposium, I want feedback on how to measure visual access and agency, and how to bring these projects together into one framework. I’m also looking forward to the panel’s advice on building a research career as a disabled researcher.

If you’re at UIST 2026, come say hi!

If you want to read more about why I care so much about designing with the vision we have, check out my post on why my needs are not “special”.

I’m grateful to my advisors, Takeo Igarashi and Ariel Shamir, and to everyone who shared their experiences in these studies.




If you found this useful, please cite the paper:

Sechayk, Y. (2026). Visual Communication for Low-Vision Information Access: From Personalized Highlights to AI Agents. In Adjunct Proceedings of the 39th Annual ACM Symposium on User Interface Software and Technology (UIST Adjunct ‘26). ACM. https://doi.org/10.1145/3830397.3841706

or as a BibTeX entry:

@inproceedings{sechayk2026visualcommunication,
  author    = {Sechayk, Yotam},
  title     = {Visual Communication for Low-Vision Information Access: From Personalized Highlights to AI Agents},
  booktitle = {Adjunct Proceedings of the 39th Annual ACM Symposium on User Interface Software and Technology},
  series    = {UIST Adjunct '26},
  year      = {2026},
  publisher = {Association for Computing Machinery},
  address   = {Detroit, MI, USA},
  doi       = {10.1145/3830397.3841706}
}

References

  1. UIST
    First page of the doctoral symposium paper Visual Communication for Low-Vision Information Access, showing the title, author, abstract, and a teaser figure of the research trajectory from VeasyGuide and On-Cursor Visual Context to Visual Context for AI and future bidirectional visual communication with AI agents.
    Visual Communication for Low-Vision Information Access: From Personalized Highlights to AI Agents
    Yotam Sechayk
    In Adjunct Proceedings of the 39th Annual ACM Symposium on User Interface Software and Technology (UIST Adjunct ’26), 2026
    Note: doctoral symposium
  2. ASSETS
    First page of the VeasyGuide paper, showing the title, authors, and a teaser figure of the VeasyGuide video player with highlighted instructor actions and its personalization settings panels.
    VeasyGuide: Personalized Visual Guidance for Low-vision Learners on Instructor Actions in Presentation Videos
    Yotam Sechayk, Ariel Shamir, Amy Pavel, and Takeo Igarashi
    In Proceedings of the 27th International ACM SIGACCESS Conference on Computers and Accessibility (ASSETS ’25), 2025
  3. CHI
    First page of the On-Cursor Visual Context paper, showing the title, authors, abstract, and a teaser figure of the Dynamic Context and Mini-map pointer interactions for reading charts with low vision.
    Improving Low-Vision Chart Accessibility via On-Cursor Visual Context
    Yotam Sechayk, Hennes Rave, Max Rädler, Mark Colley, Zhongyi Zhou, Ariel Shamir, and Takeo Igarashi
    In Proceedings of the 2026 CHI Conference on Human Factors in Computing Systems, 2026

Enjoy Reading This Article?

Here are some more articles you might like to read next: