Meaningful Alt Text for Service Photography

A consultancy homepage often leads with a photograph of a workshop, a job site, or a team in conversation. Sighted visitors read the image in a glance and move on to the offer. Screen reader users, people who browse with images off, and search engines encounter the same photo only through its text alternative. When that alternative is missing, stuffed with keywords, or copied from a filename, the photo stops doing its job for a large share of the audience.

WCAG Success Criterion 1.1.1 Non-text Content (Level A) requires a text alternative that serves the equivalent purpose of non-text content—not a literal inventory of every visual detail. The W3C Web Accessibility Initiative (WAI) Images Tutorial and WebAIM’s Alternative Text article turn that requirement into a practical decision: classify the image by purpose, then write (or deliberately omit) text that matches that purpose.

---

Why service photography needs a purpose test

W3C’s Understanding document for SC 1.1.1 states the goal plainly: non-text information should be available to more people. Text alternatives can be spoken, shown as braille, displayed when an image fails to load, or indexed by search. The intent is equivalence of purpose—the same reason the photo is on the page—rendered in a form assistive technology can use.

That framing matters for service sites. A hero shot of a kitchen remodel is not there to document tile colors for a catalog; it is there to show the kind of work the firm does. A stock handshake beside a paragraph about “professional partnerships” often adds no information beyond mood. The same file could be informative on a case-study page and decorative on a marketing band. Context decides.

WebAIM opens with the same caveat algorithms cannot solve: software may recognize a maple leaf, but only an author knows whether that leaf stands for Canada or simply illustrates a tree. Authors must supply alternative text that represents content and function inside the page.

---

How WAI classifies images—and what to write

The WAI Images Tutorial organizes decisions by image type. For a typical service site, four categories cover most photography:

Image type	What WAI expects	Service-site example
Informative	Short description of the essential information	Project photo: “Finished open-plan kitchen with oak island and pendant lighting”
Decorative	Null alt="" so assistive tech can ignore it	Soft-focus texture behind a testimonial already stated in text
Functional	Description of the link or button action, not the artwork	Thumbnail linking to a case study: destination or project name
Images of text	Same words as appear in the image (prefer real text when possible)	Logo lockup: firm name; avoid rasterized headlines when CSS text works

WAI’s informative-images guidance stresses meaning over literal description. A diagram of a bottle cap gets “Push the cap down and turn it counter-clockwise,” not a catalog of shapes. Applied to photography: name what the visitor is meant to understand—the service context, the completed outcome, the setting—rather than camera angle or wardrobe color unless those details carry the message.

WAI’s decorative-images page is equally direct. Borders, ambiance “eye-candy,” and photos already described by adjacent text should use an empty alt. Screen readers then skip the image instead of announcing filler. WebAIM’s handshake example makes the same point: if deleting the image would lose no important content, alt="" is usually correct—and stuffing SEO phrases into alt is not a substitute for real body copy.

For functional images, both sources agree: when an image is the only content inside a link or button, the alternative must carry the destination or action. WebAIM notes that empty alt here can force screen readers to fall back on filenames or URLs. When caption text sits inside the same link as the image, empty alt on the photo avoids double announcement.

---

A practical writing pattern for service photos

Treat each photo like a short brief for someone who cannot see it.

1. Ask what the photo is doing. Proving capability? Showing a location? Filling empty space? Linking to a project?
2. Check nearby text. If a caption or paragraph already names the subject completely, prefer alt="" (WAI decorative example 3; WebAIM’s adjacent-text case).
3. Write the equivalent, then cut. WebAIM’s default: accurate, succinct, non-redundant; typically a few words, occasionally a short sentence. Do not open with “image of” or “graphic of”—screen readers already announce the graphic role.
4. Match function for linked images. Destination or action first; avoid “click here” and “link to.”
5. Keep every img tagged. WebAIM requires an alt attribute on every image, including alt="" for decorative ones. Omitting the attribute is a different failure from an intentional null.

A brief analogy: alt text is a label on a sample board in a showroom—enough for someone to know which finish they are holding, not a full materials essay. When the essay belongs somewhere, put it in visible body text or a long description, not in a stuffed attribute.

WAI’s complex-images guidance applies when a chart or diagram cannot fit in a short alt: give a brief identifying alternative, then provide the full equivalent nearby (table, adjacent summary, or linked description). Most service photography will not need that path; most service infographics will.

---

Limits and tradeoffs worth stating

SC 1.1.1 allows decoration, formatting, and invisible non-text content to be implemented so assistive technology can ignore it—null alt and CSS background images for pure decoration are the common techniques. That does not mean every atmosphere photo should vanish from the accessibility tree by reflex. If the photo is the only evidence that the firm works on historic façades or industrial sites, it is informative; describe the essential cue.

WebAIM also warns against two common overcorrections: using alt to inject marketing claims that are not in the image, and writing novels when a few words would do. Overlong alternatives slow keyboard and screen reader users who are trying to reach the offer. Unduly clever keyword lists fail both accessibility and trust.

Judgment remains involved. WAI’s decision tree covers many cases but not all; authors still decide based on usage, context, and content. When unsure, test with a screen reader on the live page: does the sequence of announcements match the visual story a sighted colleague would retell in one breath?

---

Practical takeaways for your next website

1. Classify before you write. Informative, decorative, functional, or text-in-image—pick one purpose per photo.
2. Prefer real text for headlines and CTAs. Reserve images of text for logos and unavoidable brand marks; keep the same words in alt when an image of text remains.
3. Audit heroes and galleries together. Empty alt on every ambiance band; purposeful short descriptions on project proof shots; destination-aware alt on linked thumbnails.
4. Never leave alt missing. Use alt="" deliberately for decoration; never omit the attribute or paste a CMS filename.
5. Review after copy changes. If surrounding text starts carrying the photo’s meaning, simplify or null the alternative so announcements stay lean.

---

Ready to Discuss Your Website?

If you are planning a new website, a service redesign, or custom development for your business, we’re here to help shape the work—including photography systems that stay clear for every visitor.

• Explore Our Services: Web Design · Web Development · Website Redesign
• Start a Conversation: Tell us about your project via our Contact Form or email us directly at [email protected].