Should image alt text describe the file or its purpose?

Read the image together with its surrounding sentence

Start with the page’s purpose and the nearby copy. If the product description already gives dimensions, repeating the entire list may not help. A visible timber joint or armrest shape might be worth describing when it informs a choice. Do not infer hidden properties from a photograph and present them as facts.

The W3C decision tree distinguishes meaningful images described according to context from purely decorative images given an empty alt attribute. Intentionally empty alt and a missing attribute are different conditions. Make the decision around the image’s role, rather than trying to reduce a warning count in an SEO tool.

Check the function of an image inside a link

When an image is the only content of a category link, it needs an accessible name that explains the destination. A purpose-focused phrase may be more useful than “chair photograph”. If the same link already contains a visible category heading, consider whether the image description would unnecessarily repeat that name.

An image and heading implemented as separate links create two focus stops. Review that structure while preparing the text. Giving an editor a spreadsheet of descriptions is not enough: the developer’s link, button and label relationships affect the final meaning. Inspect the result in the browser and with the relevant assistive technology.

One drawing, three roles

Do not compress a whole diagram into one field

A process diagram or data chart can carry more information than a short photograph description. Briefly identify what it shows and provide the detailed explanation as real page text. Someone unable to access the image should still be able to understand its important conclusion.

For a three-stage delivery diagram, explain the stage names, sequence and meaningful connections. Avoid colour-only directions: use the box’s name rather than “continue from the green box”. Check the text equivalent for meaningful words that appear only in the image. Filling one narrow alt field with a long list is not the only available approach.

Deliver Turkish and English versions together

When the page language changes, meaningful image text and its alternative should follow. Keep product names and technical terms consistent. An automatically exposed filename in English is not fixed by a carefully written Turkish description. Give each language a separate place in the content inventory.

Read the description again whenever the image changes. A detail visible in an earlier photograph may disappear in a new crop. Instead of copying one description across a gallery, ask whether each frame has a distinct purpose. If several images add nothing new, simplifying the selection may be a better editorial decision.

Finish the review with meaning and structure

Record the image source, usage rights, page role, alt text and any extended explanation together. What information disappears if the image does not load? Does an image link still make sense without the picture? These questions help an editor begin the review; technical accessibility assessment continues beyond them.

Our mobile image-direction guide addresses which detail survives a crop. The Erhan Mobilya project page is a real presentation reference; the chair example here is not a claim about that client’s products. Treat text alternatives as content decisions within the website handover, rather than empty fields to fill at the end.