ARIA13: Name Your Landmarks or Lose Your Users

Keisha
digitalwcagariascreen readerslanguage access

Keisha · AI Research Engine

Analytical lens: Community Input

Community engagement, healthcare, grassroots

AI-assisted · Source-linked · Editorially reviewed · Methodology

Trust note

This article was drafted with AI assistance, reviewed against accessibility.chat editorial standards, and should be treated as research and education rather than legal advice. We prioritize primary sources and correct material errors.

Top view of a vintage Braille typewriter and Braille paper on a wooden floor, highlighting accessibility tools.
Photo by Thirdman on Pexels

Before ARIA landmarks, screen reader users navigated pages the hard way — heading by heading, link by link, with no structural map of what they were moving through. Landmarks changed that. Then developers started implementing landmarks without labels, and for pages with multiple regions of the same type, the map became useless again.

WCAG 2.2 Technique ARIA13 (opens in new window) addresses that regression directly. It describes how to use aria-labelledby to attach visible, on-page text to landmark regions — so assistive technology users don't just know that a landmark exists, but what it is.

The Technique

ARIA13 is one of the sufficient techniques for meeting WCAG 2.1 Success Criterion 1.3.1: Info and Relationships (opens in new window). The core mechanism is straightforward: add aria-labelledby to a landmark element, point it at the id of a heading or text already visible on the page, and assistive technology announces that label when a user enters the region.

The W3C's official code example shows this in action with a complementary landmark:

HTML
<div role="complementary" aria-labelledby="hdr1">
<h1 id="hdr1">Top News Stories</h1>
...
</div>

The heading does double duty — it's visible to all users and programmatically names the region for screen reader users. No redundancy, no hidden text, no maintenance burden.

For application landmarks, ARIA13 extends this to include aria-describedby for static descriptive prose:

HTML
<div role="application" aria-labelledby="p123" aria-describedby="info">
<h1 id="p123">Calendar</h1>
<p id="info">This calendar shows the game schedule for the Boston Red Sox.</p>
<div role="grid">
...
</div>
</div>

The aria-labelledby attribute can also accept multiple space-separated IDs, allowing composite labels drawn from multiple on-page elements — useful for complex layouts where a single heading doesn't fully describe a section.

Why This Matters

Landmarks without labels create a specific kind of confusion. When a page has one <nav>, announcing "navigation" is sufficient. When a page has three — site navigation, breadcrumb navigation, in-page section navigation — a screen reader user cycling through landmarks hears "navigation, navigation, navigation" with no way to distinguish them.

For keyboard-only users relying on landmark navigation shortcuts (available in NVDA, JAWS, VoiceOver, and Narrator), this forces a fallback to slower heading-by-heading exploration. The landmark system, designed to save time, becomes a dead end.

Users with cognitive disabilities face a related problem. Clear, consistent region labels reduce the cognitive load of orienting to a new page. When landmarks are present but unnamed, the structural promise of the page — this section does this, that section does that — goes unfulfilled.

This is not a theoretical edge case. Pages with complex layouts — dashboards, news aggregators, government portals, healthcare patient portals — routinely deploy multiple instances of the same landmark role. Without ARIA13 (or its equivalent aria-label approach), every one of those regions is functionally anonymous to assistive technology.

How to Apply This

In code review: Flag any role="navigation", role="complementary", role="region", or role="application" that appears more than once on a page without an accessible name. Single instances of <main>, <header>, and <footer> are typically exempt — they're unambiguous by position — but even these benefit from labels on complex pages.

In automated testing: Most automated tools will flag unlabeled role="region" elements (since the ARIA spec (opens in new window) requires an accessible name for region to be exposed as a landmark at all). Duplicate unnamed landmarks of other types are harder to catch automatically — this is exactly the kind of contextual gap documented in our research on automated testing limitations. A linter can confirm aria-labelledby is present; it cannot confirm the label is meaningful.

In design: Ensure every distinct section of a layout has a visible heading or label. If a region doesn't have visible text that describes it, that's a design problem before it's a code problem. ARIA13's elegance is that it reuses existing content — if there's no content to reuse, the region may not be clearly defined for any user.

Quick wins vs. longer fixes:

  • Quick: Add aria-labelledby to existing landmarks that already have adjacent headings. This is often a one-line change per region.
  • Longer: Audit designs that use unlabeled visual groupings and introduce visible, meaningful headings. This requires design and content collaboration, not just a developer fix.
Landmark RoleRequires Label When...ARIA13 ApproachSC Reference
navigationMultiple <nav> elements on pagearia-labelledby pointing to heading or visible text1.3.1 (opens in new window)
complementaryMultiple sidebar/aside regionsaria-labelledby on the wrapping element1.3.1 (opens in new window)
regionAlways (required to be exposed as landmark)aria-labelledby or aria-label1.3.1 (opens in new window)
applicationAlwaysaria-labelledby + aria-describedby for context1.3.1 (opens in new window)
main, banner, contentinfoMultiple instances or complex pagesaria-labelledby recommended1.3.1 (opens in new window)

The Language Access Intersection

One dimension that's easy to miss: landmark labels are part of the accessibility layer that traditional translation services routinely skip. A government portal translated into Spanish may render all visible text correctly while leaving aria-labelledby references pointing to English IDs — or worse, to IDs that no longer exist after a translation pass restructures the DOM.

This is the compliance gap that idioma.chat (opens in new window) is built to close. Unlike surface-level text translation, it handles the full accessibility layer — ARIA labels, alt text, form validation messages, and dynamically loaded content — so the landmark structure works for Spanish-speaking screen reader users, not just English-speaking ones. Under Title VI (opens in new window) and the ADA together, a site that passes WCAG AA in English but breaks its accessibility layer in translation isn't serving the communities it's legally required to reach. Compliance teams need to audit both mandates together, not in separate workstreams.

CORS Perspective

Through the CORS framework, ARIA13 is a clean example of where all four pillars converge on a single low-cost fix. From a Community lens, unnamed landmarks disproportionately affect screen reader users navigating complex government and healthcare portals — exactly the high-stakes contexts where orientation failures have real consequences. Operationally, this is a high-impact, low-effort change that belongs on every team's chop list: existing headings become landmark labels with one attribute. The Risk case is direct — unlabeled role="region" elements are a WCAG conformance failure, and organizations that treat landmark structure as decorative face the same compliance exposure documented in settlement patterns. Strategically, implementing ARIA13 correctly is also a forcing function for better design: if you can't label a landmark, you may not have defined the region clearly enough for any user.

About the Keisha lens

A community-impact lens. Frames findings around who is excluded and what a barrier means in practice, with emphasis on healthcare and grassroots access.

Keisha is an AI analyst lens, not a human staff member. It helps frame this article through a consistent accessibility perspective.

Specialization: Community engagement, healthcare, grassroots

View all articles using this lens →

Transparency Disclosure

This article was drafted with AI assistance and reviewed against our editorial methodology. We disclose that process so readers can judge the work clearly.