Alt text for screenshots: UI, dashboards, and pictures of text

Someone on your team drops a screenshot into a post. A dashboard with a number that went up. A settings panel with a red arrow drawn on it. A customer's message, cropped. It's the fastest way to show a thing, and it's the kind of image most likely to end up completely invisible.

A photo without alt text loses a picture. A screenshot without alt text loses words — often the entire point of the post, sitting right there in pixels where nothing can read them.

Every screenshot is a picture of text

Accessibility guidance is blunt about this. WCAG asks you to use real text rather than images of text wherever the design allows it, because text baked into an image can't be resized, recolored, translated, or selected. Logos are the accepted exception. Screenshots usually aren't — they're a shortcut.

That's not an argument for never posting one. It's a reminder that when you do, the words in that image have to exist somewhere else. Alt text is usually where that debt gets paid.

It's true that some screen readers can now analyze an image on demand — JAWS has an AI description feature, and OCR tools have been around for years. But that's the reader doing extra work to recover something you could have handed them in one sentence. It's a fallback, not a plan.

Describe the finding, not the furniture

The most common mistake with a dashboard screenshot is describing the object instead of the reason you posted it.

The weak version tells a listener that a dashboard exists. The strong version tells them what you'd have said out loud. Ask why you took the screenshot; that answer is your alt text, not the interface around it.

The same rule covers UI walkthroughs. If you're showing where a control lives, name the control and its location — not the whole window.

When the words are the whole message

Sometimes the screenshot is just a block of text: a customer email, a policy update, a code snippet, a post you're quoting. Here "describe the image" is the wrong instruction. Transcribe it.

If it's short, put the text in the alt field along with who said it. If it's long, don't cram — write a brief alt text that names the source and points onward ("Screenshot of a customer email; full text below"), then put the actual words in the caption or post body where everyone can read them. Real text also survives translation, search, and copy-paste. Your screenshot doesn't.

One convention worth keeping: unlike photos, leading with "screenshot" is fine here, and often useful. It isn't filler the way "image of" is. It tells a listener the frame is a screen, which changes how they read everything after it.

A ten-second test

Before you publish, read your alt text back and ask whether someone could act on it without seeing the picture. If the screenshot is proof of a number, is the number in there? If it's a how-to, is the control named? If it's a quote, are the words present?

Screenshots are the images with the most real information in them and the least chance of being described. That's a bad combination, and it takes about ten seconds a post to fix.