Published lesson · 30 minutes

Review structure and accessibility

Objective: Audit an HTML page for meaningful structure, keyboard access, readable link text and useful alternatives.

Understand the idea

Review structure and accessibility works best when the learner can explain the reason behind each step, not just copy a result. Accessibility review combines semantic code with a short task-based check; passing one automated rule cannot prove every person can use the page.

A learner reviews a public information page by navigating without a mouse, reading its headings and checking whether an image alternative adds information. Treat the names and details as invented practice information; the example is for learning a method and does not describe a live service.

A dependable sequence is: Check document title, heading order, landmarks, link purpose, image alternatives, form labels and keyboard focus; fix the clearest barrier first. Write down the important decision before you begin so another person can follow the reasoning.

Use descriptive alt text for informative images and empty alt text for decoration. Do not use a file name or repeat nearby text as an alternative. Compare the result with the objective, then change one thing at a time if the first attempt does not work.

Write an accessibility checklist with one manual test for navigation, forms and images. Explain one assumption that would need checking before anyone used a similar result outside the classroom.

Keep a short record of the choices you made and the evidence you used to check them. A useful practice result is understandable by another learner, stays within the stated scope and makes its limitations visible before anyone relies on it.

Worked examples

Review structure and accessibility: practice example

Explore how review structure and accessibility supports the lesson objective with a small synthetic example.

index.html

<main><h1>Check the page structure</h1><h2>Contact</h2><a href="mailto:example@example.test">Email the practice team</a><img src="map.png" alt="Map showing the entrance beside the main road"></main>

Practice tasks

  1. Explore review structure and accessibility

    Use the worked example for “Review structure and accessibility”. Change one small detail to suit a different synthetic community situation, then explain what you expected and how you checked whether the change still met the lesson objective.

  2. Build a HTML practice example

    Create a small practice result that demonstrates this objective: Audit an HTML page for meaningful structure, keyboard access, readable link text and useful alternatives. Use only synthetic information, keep the first version focused, and write down one limitation that a later version should address.

  3. Review and explain the result

    Review your “Review structure and accessibility” result as if another learner will use it without your explanation. Identify one strength, one exact point that may be unclear, and a revision that would make the result easier to understand or use.

Review structure and accessibility becomes easier when you check document title, check the result and explain the choice to another learner.

Course overview