Research Guides
An Image Review Worksheet for Accessibility and Search
A photograph, diagram or button icon can carry information that the surrounding page never explains. Reviewing those images gives you a concrete editing task: decide what each image contributes, check whether that meaning is available in text and record the changes needed.
Start with a few important public pages you control. This worksheet combines an editorial review with a small set of implementation checks. It is an initial review, not a full accessibility assessment or a forecast of search performance.
Start with the image's job
Choose one page and read it in order. For each image, ask what a visitor would lose if it were unavailable. Write the answer before drafting alternative text. “Shows the location of the release catch” is a useful purpose. “Needs keywords” does not explain what the visitor needs.
The W3C Web Accessibility Initiative's alternative-text decision tree distinguishes images that convey information, perform a function, repeat nearby content or add decoration. A simple informative image needs a concise alternative that communicates its meaning in the particular page context. If meaningful text appears only inside an image, include that text in its alternative unless the image serves a function that needs a different label.
Use that guidance to make a decision for each placement. If the same photograph appears on a product detail page and in an unrelated background collage, review both uses rather than approving one description for every occurrence.
Keep one worksheet row per placement
A small review is easier to finish when every row ends in an owner and a check. Use these fields:
- Page and image: Page address, section heading and image filename or address, where available.
- Purpose: The information, action or decoration the image provides in this location.
- Current evidence: Existing alternative text, nearby wording and any relevant link or button destination.
- Proposed change: Exact replacement text, an empty alternative where appropriate, or the additional explanation required.
- Implementation owner: The person responsible for the page content or component.
- Verification: Date checked, result and any unresolved question.
Distinguish “alternative text is missing” from “alternative text is present but empty.” Record what you actually inspected. If the editor hides an image's settings, leave that field unresolved until someone can inspect the rendered page or markup.
Begin with a batch you can review in one sitting. Include a useful mix: an instructional photo, a linked image and any chart readers need to understand. Expand to shared templates after the first examples have clear decisions.
Leave decorative images quiet
For a decorative image implemented with an HTML img element, W3C recommends an empty alt value, written as alt="". Omitting the attribute is different: some screen readers may announce a filename instead. Whether an image is decorative depends on its purpose in the page. See W3C's decorative-image guidance.
Record the reason for an empty value. “Adds a patterned border and conveys no information” is more useful to a future editor than “blank is fine.” If someone later uses that image to carry a warning or instruction, reopen the decision.
Review linked images as controls
An image that supplies a link or button's only label needs an alternative that explains the destination or action. Describing the icon's shape may leave the visitor guessing what happens. W3C also shows that an image inside a link can have empty alternative text when the same link already contains adequate text and the image adds nothing further. W3C's functional-image examples explain the distinction.
For a fictional catalogue, an image-only link to a fitting guide could use “Open the fitting guide” rather than “Blue document icon.” Check the actual destination before accepting that wording. If the image sits beside those same words inside one link, avoid making the label repeat unnecessarily.
Keep this review scoped to the control as a whole. Ask the implementer to confirm how its accessible name is produced if another label mechanism is involved. Do not overwrite working labels merely to make an image report show more populated fields.
Give charts an explanation people can use
A short label cannot carry every relationship in a complex diagram. W3C describes a two-part approach: a brief text alternative identifying the image, plus a longer explanation of its essential information. That explanation may include values, relationships and trends. The complex-images tutorial provides implementation options.
Suppose a fictional repair business publishes a chart with 18 enquiries in April, 24 in May and 21 in June. The worksheet could propose a short alternative identifying the enquiry chart and pointing to the adjacent explanation. The visible explanation would give the three values, name the months and say that May had the most enquiries. Include any distinctions conveyed by the chart's labels or legend.
Verify the proposed explanation against the underlying figures. If the chart's source cannot be found, mark the numbers for confirmation rather than reconstructing them from a blurry screenshot. These figures are invented to illustrate the review, not business results.
Check a few search-related details separately
Google's image SEO guidance recommends standard HTML image elements. Google can discover an image through the src attribute of an img element, including within picture; it does not index CSS background images. For responsive images, Google recommends retaining an img element with a fallback src.
The same guidance recommends relevant surrounding text and short, descriptive filenames. It says filenames offer only light clues about the subject. Alternative text should be useful in context rather than packed with keywords.
Add an implementation note when an important content image is available only as a CSS background, or when the image shown does not match its surrounding explanation. Leave genuinely decorative backgrounds out of that search-discovery task. If you propose renaming an existing file, list the references that would need updating before anyone changes its address.
Treat these checks as separate from the editorial decision about meaning. Record a specific observation and requested fix, rather than giving every image a vague “SEO score.”
Publish a small batch and check the result
Before editing, save the original wording and the relevant page location. Agree on who will change the content and who will verify it. If one shared component affects many pages, test a representative page before applying the change more broadly.
After publication, inspect the actual page. Confirm the correct image loads, the alternative text matches the agreed decision, linked images have meaningful labels and longer chart explanations are present and connected clearly to their images. Check that nearby text does not contradict an updated visual.
Automated tools can help identify potential problems, but W3C notes that they cannot evaluate every accessibility issue and can produce misleading results. Human judgement remains necessary. See W3C's guidance on evaluating tools.
Close the worksheet with specific outcomes: “Added the missing instruction,” “Confirmed the decorative image has an empty alternative,” or “Chart figures still need an owner.” The useful result is a set of verified improvements and a short, honest list of what remains.