Build a structure people can navigate
Give the page a descriptive main heading and organise sections with headings in a logical order. A heading names the section; it is more than a visual style. Do not skip levels to achieve a particular appearance. W3C WAI’s headings tutorial explains how people use them to navigate.
Put key information early, use lists for actual sets of items, explain less familiar abbreviations and make process steps explicit. Clear structure also helps review, translation and maintenance.
Write useful links and image alternatives
A link should identify its destination or action when read out of context. Replace “click here” with the document, service or step name. When repeated link labels lead to different destinations, add enough context to tell them apart.
For an informative image, write alternative text that conveys its purpose on this page rather than mechanically listing objects. A decorative image may have empty alt text. W3C WAI’s image examples distinguish these cases. Also check image rights and quality using the visuals guide.
- Descriptive headings.
- Links understood out of context.
- Alternative text suited to image purpose.
Handle tables, documents and media
Use a table when rows and columns make data easier to compare; identify headers and explain units. Do not use a table simply to position text. For a chart, state the central finding and provide enough underlying information to understand it.
Before publishing a PDF or video, check the file’s accessibility and relevant alternatives such as captions and transcripts. A link to a file does not make its content accessible. Where the information is essential, a structured HTML version is often easier to read and update.
Build a check into publishing
Ask another person to review a representative page: can they understand headings, links and instructions without spoken help? Navigate by keyboard, enlarge the text and check alternative text in the final HTML. An editor preview may differ from the published page.
Repeat these checks for new content and translations. If a template prevents correct headings, labels or tables, report it to the technical team. The accessibility testing guide covers broader page checks.
- Published page reviewed.
- Translations and files checked.
- Template defects reported to the owner.