Skip to content
Asuruas
How to

How to write alternative text

A focused implementation guide for alternative text, covering evidence, ownership, implementation decisions, quality control, and verification.

Start reading
Implementation guide

alternative text

Prepare the change, implement it through the correct source system, test representative cases, deploy safely, and retain verification evidence.

Primary topicalternative text

A focused implementation guide for alternative text, covering evidence, ownership, implementation decisions, quality control, and verification.

Operating outcomeAccountable improvement

Remove barriers from important user tasks and make accessibility part of routine website operations.

Review statusMaintained resource

Reviewed for accuracy, clarity, and operational use.

01

Step-by-step

  1. 01

    Identify the image function

    Decide whether it communicates information, performs an action, identifies something, or is decorative.

  2. 02

    Describe the meaningful information

    Write the information a person needs in the current context rather than every visual detail.

  3. 03

    Avoid repetition

    Do not repeat adjacent text or begin every value with 'image of'.

  4. 04

    Handle decorative images correctly

    Use an empty alt value when the image adds no meaningful information.

  5. 05

    Test the page without the image

    Confirm the remaining text and alternative communicate the intended task.

02

Verification

  • The implementation matches the visible page and intended audience task.
  • The result works on mobile and with keyboard operation where applicable.
  • Links, code, schema, and instructions have been checked in production.
  • The expected business or user outcome can be measured.
  • An owner and review trigger are recorded.
03

Before you change the website

  • Define the purpose and expected result of alternative text.
  • Capture the current state using semantic structure, keyboard operation, focus order, labels, names, contrast, alternatives, errors, and assistive-technology behaviour.
  • Identify the source template, component, plugin, content owner, and release path that controls the output.
  • Prepare a test case, approval path, backup or rollback method, and post-release verification plan.
04

Quality-control checks for alternative text

  • Repeat automated checks, complete the relevant manual task, and record the browser and assistive-technology context.
  • Check representative page types and edge cases instead of confirming only the example used during implementation.
  • Confirm the change did not create repairing markup without checking the complete keyboard and screen-reader task.
  • Record the implementation date, owner, release reference, evidence, and next review trigger.
Next useful action

Turn alternative text into an accountable record.

A tested implementation of alternative text with deployment notes, rollback context, and retained verification.