Skip to main content
Votre navigateur est trop ancien pour afficher correctement ce site. Veuillez passer à la dernière version de Chrome, Edge, Firefox ou Safari.
Back to WCAG Database
Level AAAWCAG 2.1

1.3.6 Identify Purpose

The purpose of UI components, icons, and regions can be programmatically determined.

Last reviewed: September 9, 2026

Understanding 1.3.6

This AAA criterion extends the idea behind 1.3.5 beyond simple user-data input fields to the purpose of UI components, icons, and page regions generally, so that assistive technologies, browser extensions, and personalization tools (like symbol sets for users with cognitive or learning disabilities) can recognize and adapt common controls, such as search fields, navigation menus, or social-media icons.

How to Meet It

Use standard HTML landmark elements (nav, main, header, footer), ARIA landmark roles, and applicable HTML5 attributes (like autocomplete or well-known icon conventions) so tools can programmatically recognize the purpose of components and regions, not just of form fields.

Code Examples

INCORRECT
<div class="nav">...</div>
<div class="main-content">...</div>
CORRECT
<nav aria-label="Primary">...</nav>
<main>...</main>

Frequently Asked Questions

How does this differ from 1.3.5 Identify Input Purpose?

1.3.5 (Level AA) is narrowly scoped to input fields that collect information about the user. 1.3.6 (Level AAA) is broader, covering the purpose of general UI components, icons, and page regions beyond just form inputs.

Related Success Criteria

1.3.1 Info and Relationships1.3.2 Meaningful Sequence1.3.3 Sensory Characteristics1.3.4 Orientation

Quick Facts

  • Criterion1.3.6
  • LevelAAA
  • IntroducedWCAG 2.1

Automate Compliance

AccessiSight automatically scans and identifies 1.3.6 issues in your codebase.

Try Scanner Free