Aller au contenu
Clearfront Digital
Menu
← Blog · article en anglais

How to write useful image descriptions for your website

Published

A useful image description explains what the image contributes to the page. It is not a place to list every visible detail or repeat a string of search terms.

Start with a simple question: if someone cannot see this image, what would they miss here? The answer may be a short description, the purpose of a link, or nothing at all if the image is purely decorative.

Describe the point of the image

Alternative text, often called alt text, can be read by a screen reader or displayed when an image cannot load. The right wording depends on the image and its surrounding content, not just the subject of the photograph.

Imagine a roofing company showing a finished metal roof on a project page. If the image illustrates the material and result, “Standing-seam metal roof on a single-story house” gives a reader useful context. “Roofing contractor, best roofing company, roof repair” does not describe the picture. These are hypothetical examples, not claims about a real project.

Be specific when the detail matters, but avoid guessing. If you cannot verify the location, person or material, leave it out or check with someone who can. Do not put a customer’s name or address in a description unless it is appropriate and authorized.

Look at the surrounding words

A caption or nearby paragraph may already convey the same information. Repeating it word for word can make the page cumbersome to navigate. For an image that adds no information beyond nearby text, an empty alt attribute may be appropriate. That is different from leaving the attribute out entirely.

The same photograph can need different treatment in a different place. A team photo that identifies the people on an About page may be informative; a small background image used only for atmosphere may be decorative. W3C’s decorative-image guidance explains this distinction.

Name the action when an image is a control

If an image alone is used as a link or button, its accessible name should tell someone what the control does or where it leads. A magnifying-glass icon that starts a search needs a name such as “Search,” rather than “magnifying glass.” If visible text already names the same control, avoid making the name repeat unnecessarily. Ask the developer to check the complete control, not only the image file.

W3C’s functional-image examples show how the image and its surrounding link or button work together.

Give complex information more room

A short alt attribute is not enough to convey every value in a detailed chart or diagram. Include the important information in accessible text or a suitable table on the page, then use the image’s alternative to identify it and direct readers to that information. Do not rely on text embedded in an image as the only way to deliver essential details.

Review the page, not just the media library

Before publishing, read the page in context and check a few representative images with a screen reader. Confirm that descriptions are useful, decorative images do not create unnecessary repetition, and image-only controls have meaningful names. A content management system may have a decorative-image option; verify the published result if you are unsure what it produces.

For an image that is difficult to classify, use W3C’s alt decision tree and ask your developer or accessibility specialist. This is a practical starting point, not an accessibility audit or certification.