What it checks: Presence of main landmark (main element or role="main").

Why it matters: Landmarks help screen reader users navigate page structure quickly.

How to fix:

• Use semantic HTML5 elements: <main>, <nav>, <header>, <footer>
• Or add role attributes: role="main", role="navigation"

What it checks: Whether all form inputs have associated labels.

Why it matters: Labels tell users what information is needed and are read by screen readers.

How to fix:

• Use <label for="input-id"> for each input
• Or use aria-label attribute
• Or wrap input in label element

What it checks: Whether all buttons have accessible text.

Why it matters: Screen readers need text to describe what a button does.

How to fix:

• Add text content inside buttons
• For icon buttons, use aria-label
• Or use visually hidden text

What it checks: Whether image alt text is descriptive vs generic.

Why it matters: Generic alt text like "image" doesn't help users understand the image.

How to fix:

• Write descriptive alt text that explains the image content
• Avoid "image of...", "photo of...", "picture of..."
• For decorative images, use empty alt=""

What it checks: Whether link text is descriptive vs generic.

Why it matters: Users should understand where a link goes without surrounding context.

How to fix:

• Replace "click here" with descriptive text
• Replace "read more" with "Read more about [topic]"
• Link text should make sense out of context

What it checks: Whether data tables have <th> elements.

Why it matters: Table headers help screen readers associate data cells with their headers.

How to fix:

• Use <th> for header cells
• Add scope="col" or scope="row" as appropriate
• Use <caption> to describe the table purpose

What it checks: Presence of a skip-to-content link.

Why it matters: Skip links let keyboard users bypass repeated navigation.

How to fix:

• Add a visually hidden link at the top of the page
• Link should point to #main-content or similar
• Make visible on focus for keyboard users

What it checks: Whether form inputs have autocomplete attributes.

Why it matters: Autocomplete helps users fill forms faster and reduces errors.

How to fix:

• Add autocomplete="email" for email fields
• Add autocomplete="name" for name fields
• Use appropriate autocomplete tokens