Synthetic example report

People who cannot see an image need the information or function it contributes.

1. Find the image shown in the evidence in your page or media editor.
2. If it conveys information, describe that information in context. If it acts as a link or button, describe its function.
3. Use an empty alt attribute only for a purely decorative image. Do not guess an image’s meaning from its filename.

Illustrative HTML: adapt this example to your actual page. It is not a ready-to-apply patch.

<!-- Informative image: replace the example description. -->
<img src="photo.jpg" alt="Describe the relevant information here">

<!-- Purely decorative image only: -->
<img src="decoration.svg" alt="">

Verify the change: Review the image and surrounding content together. Run the same URL again, then check the reading experience. Presence of alt text alone does not establish its quality.

W3C WAI guidance: Image has no text alternative in its HTML

A clear label tells people what information a form field expects.

1. Find the affected field in your form editor.
2. Add a visible, meaningful label. A placeholder alone is not a lasting label.
3. In HTML, connect the label’s for value to the field’s unique id. Keep existing field names and submission behavior.

Illustrative HTML: adapt this example to your actual page. It is not a ready-to-apply patch.

<label for="contact-email">Email address</label>
<input id="contact-email" name="email" type="email">

Verify the change: Click the visible label and confirm focus moves to its field. Test the field’s name and instructions with a screen reader, then recheck the published URL.

W3C WAI guidance: Form control has no name in its HTML

People need to know what a button will do before activating it.

1. Find the affected button and confirm its real action.
2. Add clear visible text that describes that action. For an icon-only button, provide an accessible name that matches the action.
3. Preserve its existing type, handlers and form behavior. The example is illustrative.

Illustrative HTML: adapt this example to your actual page. It is not a ready-to-apply patch.

<button type="button">Save changes</button>

Verify the change: Use a keyboard and screen reader to locate and activate the button. Confirm its name and action agree, then recheck the published URL.

W3C WAI guidance: Button has no name in its HTML

A meaningful link name helps people decide whether to follow it.

1. Find the affected link and confirm its destination.
2. Add text that makes the destination understandable in context. Preserve the actual destination.
3. If an image is the link’s only content, give it text that explains the link’s function.

Illustrative HTML: adapt this example to your actual page. It is not a ready-to-apply patch.

<a href="/contact">Contact the team</a>

Verify the change: Check the link name with a screen reader and follow it to confirm the destination. Recheck the published URL; the source check cannot judge whether the wording is useful.

W3C WAI guidance: Link has no name in its HTML

A frame label helps people identify the content embedded in the page.

1. Find the embed or iframe shown in the evidence.
2. Add a concise title describing its actual content. Preserve its real source and security settings.

Illustrative HTML: adapt this example to your actual page. It is not a ready-to-apply patch.

<iframe src="/location-map" title="Map showing our office location"></iframe>

Verify the change: Check that assistive technology announces the frame meaningfully, then test the embedded content itself. A frame title does not make that content accessible.

W3C WAI guidance: Embedded frame has no name in its HTML