Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use landmark regions correctly. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | 64% | 0% |
| case-20 | ✓→✗ | ▼ Worse | 11% | 0% |
| case-22 | ✓→✓ | = Same ✓ | -8% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -25% | 0% |
| case-01 | ✓→✓ | = Same ✓ | 23% | 0% |
Landmark regions allow screen reader users to quickly identify and jump to major sections of a page, significantly improving navigation efficiency.
<header>, <nav>, <main>, and <footer><main>)aria-labelVerify that the page uses appropriate HTML5 landmark elements and that they are correctly structured.
Replace generic <div> containers with semantic landmark elements like <header>, <nav>, <main>, and <footer>.
Explain how landmark regions assist assistive technology users in navigating complex page layouts.
Review the rendered markup and interactive states that affect Use landmark regions correctly. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/landmark-regions
Other measured skills in the registry, with their headline benchmark lift.