In plain English
Having headings and labels is step one; making them useful is step two. A screen-reader user often skims a page by its headings, and tabs through a form by its labels. If those say “Section”, “Details”, or “Field 1”, they learn nothing. This rule says headings and labels must genuinely describe what they are about.
Who this is for
- Screen-reader users, who navigate by headings and rely on labels to fill forms.
- Everyone skimming, since clear headings make any page easier to scan.
How to check and fix it yourself
Read just your headings top to bottom, do they outline the page clearly? Then read your form labels, does each say exactly what to enter? Rewrite anything vague:
Heading: "Info" → "Return policy"
Label: "Field" → "Email address"
Label: "Search" → "Search products"Where we can help
Vague headings and labels are easy to miss because they look fine, they are just not helpful. We review your headings and labels for clarity and suggest descriptive wording. It pairs with structure checks in a self-check.