Writing alt text for a photograph of your own shop
What a screen reader announces when an image has no description
You're uploading twenty photos from last week's job. Under each one there's a box asking for alternative text, and so far you've just been pasting in the filename. IMG four two nine one dot jpg is not a useful description.
That's what a screen reader user hears in some setups when the field is left empty. Sometimes it's silence. Sometimes it's the filename, read aloud, number by number, meaning nothing to anyone.
An image with no alt attribute at all gets skipped entirely by some screen readers. Others announce it simply as "image." Either way, the visitor has no idea what they missed.
The photo of your finished kitchen is the one doing real work. It's the one convincing someone to call. Left undescribed, it says nothing to a meaningful part of your audience.
Multiply that across a gallery page and the loss compounds. A visitor who can't tell one project photo from another has no way to judge the quality of the work at all.
Describing the point of the photo rather than the photo
The instinct is to describe what's literally in the frame: "man standing next to white van." The better version describes why the photo is there: "Completed kitchen renovation with white oak cabinets and marble counters."
One catalogs pixels. The other tells the visitor what the page wants them to take away from it. That difference is the whole skill.
Keep it short. A sentence, not a paragraph. Skip "image of" or "photo of" at the start — a screen reader already announces that it's an image before it reads the description, so saying it twice just wastes the visitor's time.
Think about what you'd say if you were pointing at the photo out loud, in one breath, to someone who couldn't see the screen. That's usually close to the right length.
Decorative images that should be skipped deliberately
Not every image needs a description. A background texture, a divider line, a stock photo used purely for visual rhythm — none of these carry information.
Describing them out loud just adds noise. A screen reader user has to sit through it before reaching the actual content of the page.
Marking these with an empty alt attribute tells assistive technology to skip them cleanly, on purpose, rather than by accident. That's a deliberate choice, not an oversight.
Leaving the field blank without setting it this way is different, and worse — some tools fall back to reading the filename instead, which brings back the exact problem this is meant to solve.
Logos, icons, and pictures that are also links
A logo in the header is nearly always a link back to the homepage, which changes what the alt text needs to say. "Company logo" describes what the picture looks like. "Home" describes what clicking it does.
That's the information a visitor actually needs at that point on the page. The same logic applies to a shopping-cart icon, a hamburger menu, or a social icon. Describe the destination or the action, not the picture.
A social icon linking out to a review page is a good test case. "Read our reviews" tells a visitor what happens next. "Star icon" tells them nothing useful at all.
A favicon or a small trust badge in the footer, on the other hand, usually isn't a link at all. Check first — the fix depends on which one it turns out to be.
Words baked into a graphic, and where they disappear to
A phone number typed onto a banner image. A sale price laid over a photo. A slogan rendered as a styled graphic instead of live text. All of it is invisible to a screen reader unless the alt text repeats it word for word.
Search engines have the same blind spot. If the words matter, they need to exist somewhere on the page as actual text, not just as pixels shaped like letters.
This catches business owners most often on a seasonal banner: a holiday hours graphic, dropped in fast, with the actual dates baked into the image and nowhere else on the page.
The fix is simple once you spot it. Type the same words out as real text on the page, near the graphic, and the problem disappears for good.
Check the checkout page and the pricing page first. Numbers baked into a graphic there cost real money when a visitor can't read them at all.
Keeping this sane when the gallery has hundreds of photos
Nobody writes a hundred and fifty unique, thoughtful descriptions in one sitting. Nobody needs to. Group photos by what they're doing on the page.
Every thumbnail in a "recent work" gallery can share a pattern — "Bathroom remodel, location, year" — filled in per photo rather than reinvented each time. The one image actually driving a decision, the hero shot on the homepage, is the one worth the extra two minutes.
A batch pass once a quarter, going back through whatever got added since the last one, keeps the backlog from growing into something unmanageable.
The same discipline applies to text you can't touch at all. A whole document published as a picture hides its content from a screen reader completely, and it's worth knowing how that differs from a single photo.
Before you spend time describing an image, it helps to know whether you're actually entitled to use it in the first place. Once the alt text is in decent shape, running through the rest of the self-check will tell you what else on the page needs the same attention.
And if this is the first accessibility page you've landed on, the wider picture it fits inside is worth a read too.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go