Skip to main content

WCAG guide

Footer accessibility checklist

Accessible footers improve orientation, navigation speed, and trust for all users. Use this checklist to harden implementation quality across every template.

Updated 2026-02-28

Core accessibility checks

Landmarks and labels

Use one document footer landmark and label nested navigation groups with explicit aria-label values.

Keyboard navigation

Ensure all footer links are reachable by keyboard, with clear focus order and visible focus indicators.

Heading hierarchy

Use meaningful heading levels inside footer link groups so screen-reader users can scan quickly.

Readable contrast

Keep text and icon contrast compliant for normal and large text in all themes and states.

Link purpose clarity

Use descriptive link text so destinations are understandable without surrounding context.

Frequent failure modes

  • Footer columns with visual headings that are not semantic headings in HTML.
  • Navigation lists built with div and span tags instead of links and list semantics.
  • Muted legal links with insufficient contrast on smaller screens.
  • Repeated generic link text that hides destination intent from assistive users.

Run an accessibility-aware footer scan

Use the footer checker tool to detect weak footer semantics and accessibility signals at scale.

Footer accessibility FAQ

Why does footer accessibility matter?

Footers are repeated across pages, so accessibility issues are multiplied site-wide and affect every user journey.

Do footer nav groups need aria-label?

Yes, aria-labels on nav groups improve screen-reader orientation when multiple navigation landmarks exist on a page.

How often should I audit footer accessibility?

Audit after major design changes and during regular release cycles, especially if links or color tokens are updated frequently.

Footer guide cluster

Explore related guides targeting specific footer implementation and optimization intents.