Buyer guide · Practical decisions

Can AI write useful alt text for your business website?

A website team has hundreds of product photographs and empty image-description fields. AI looks like a quick way to finish the job. But a fluent description of the pixels can miss what a customer needs to know. The useful question is whether the text serves the image’s purpose on that particular page.

Published Sources checked

Read the guide ↓
01 /

Start with the job the image does

Alternative text, usually called alt text, gives a text alternative for an image. It can be read by screen readers. On a business website, it might explain a product detail, identify the destination of an image link or provide a short introduction to a more detailed diagram description.

W3C’s decision tree starts with context: whether the image contains text, performs an action, adds information or is decorative. That makes a blanket instruction to describe every image a poor publishing rule. A purely decorative image normally needs an empty alt attribute, not a sentence announcing decoration.

Treat image use as part of the content brief. The same photograph may support a product choice on one page and simply provide atmosphere on another. A media-library description is a starting point, not necessarily the right alternative everywhere that file appears.

02 /

Illustrative example: an office furniture shop

Consider a fictional UK furniture retailer updating a chair product page. This is an illustrative workflow, not a Fewzen customer result. The page already gives the model name, price and dimensions. One photograph shows the whole chair; another shows a lever underneath the seat.

The team supplies the second image with a brief: it demonstrates where the seat-height lever is. A candidate draft says, ‘Luxury ergonomic chair with an adjustable lumbar support system.’ The reviewer rejects it. The wording adds unverified claims and does not explain the detail the photograph was selected to show.

A better draft for that use is ‘Seat-height lever beneath the right side of the seat.’ The product owner checks both the visible position and the control’s function against the approved product information. If the photograph does not show the lever clearly, the answer may be a better photograph rather than a more elaborate description.

Three images, three different editorial decisions
Image useReview decision
Lever detail on the product pageDescribe the relevant control and its location after checking the product facts.
Decorative office photograph behind a headingUse the appropriate decorative treatment; do not add a room inventory.
Chair diagram showing dimensionsProvide the measurements in accessible text as well as a short image description.
03 /

Give the model a brief it can follow

Send the selected image, page heading, nearby copy, intended purpose and any approved product facts needed to understand it. Include the link destination if the image is clickable. Use an approved tool and avoid uploading unpublished customer material merely because it happens to be in the same asset folder.

Ask for a proposed treatment, a draft where needed and a separate list of uncertainties. For example: ‘This image explains the seat-height control. Draft a concise text alternative. Use only visible details and the supplied product facts. Flag anything you cannot verify separately.’ Keep review notes out of the customer-facing field.

Microsoft’s guidance for its automatic alt text tells authors to review and edit generated descriptions. The same editorial approach is useful for website drafts, although the publishing controls belong to your own content management system. Test whether AI reduces editing effort on your images rather than assuming that generation saves time.

05 /

Keep detailed information available outside the image

A short alternative cannot carry a full sizing chart or installation diagram. W3C recommends short and long descriptions for complex images. The detailed information can be provided in the page content or an associated accessible description, so readers can reach the values and relationships they need.

For the fictional chair diagram, publish the checked dimensions as text or a suitable table. Do not ask AI to estimate a measurement from the apparent size of the drawing. Supply the approved values and compare the result with them. If the diagram explains adjustment steps, preserve their order and any important conditions.

Use AI to prepare a draft from that evidence, then have the product owner verify it. A description that merely says ‘diagram of a chair’ identifies the subject but leaves the buying information unavailable.

06 /

Review the page, then expand the workflow

Pilot the process on one representative page before changing the whole catalogue. Keep the original values, proposed replacements, page location and reviewer decision. Check whether the CMS stores text per image or per placement: a global edit could change other pages that use the same asset.

Read the draft beside the image and surrounding copy. Remove unsupported material, duplicated wording and promotional phrases that obscure the useful information. Ask someone familiar with screen-reader use to check the resulting page, including links and the reading order. An automated check that finds an alt attribute cannot establish that its wording is useful.

Compare accepted drafts, correction time and recurring mistakes with writing the same descriptions manually. Small collections may be quicker to edit directly. For larger collections, approve a bounded batch and retain a way to restore earlier values. Recheck descriptions when images, products or page purposes change.

Practical answers

Before you take the next step.

Will generated alt text make the whole site accessible?

No. It addresses one part of the experience. Navigation, forms, headings, contrast and other features still need appropriate design and review.

What is a useful first step?

Choose one page that helps customers buy or enquire. List each image’s purpose, its current alternative and who can verify its meaning. Use that list as the brief for a small trial.

Work directly with Matthew

Make the publishing workflow easier to review.

Bring the content system, a representative page and the step that causes repeated work. We can discuss a practical improvement.

Explore software development ↗Discuss your project with me ↗Prefer to write? Send a message. No sensitive records needed for an initial enquiry.