Use exactly one main landmark
SkillMedialandmark-one-main is a skill for AI agents that reviews rendered HTML, interactive components, and design-system patterns for a single main landmark. It checks that a page has exactly one main content region so assistive technology users land in the right place. The agent checks native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load and use skills.
Then ask your AI: use the Use exactly one main landmark skill
What your AI can do with it
- Checks that a page has exactly one main content region
- Reviews rendered HTML and interactive components for landmark issues
- Evaluates design-system patterns related to the main landmark
- Checks native semantics first before other inspection
- Inspects keyboard behavior and focus flow
- Reviews accessible names and screen-reader output where relevant
Getting started
- Have an AI agent that can load and use skills.
- Add the landmark-one-main skill to the agent's available skills.
- Ask the agent to review a rendered page, component, or design-system pattern.
- The agent applies the skill when the review involves the main landmark and reports what it finds.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/landmark-one-main/SKILL.md and read by ahel’s review.
A single main landmark allows keyboard and screen reader users to jump directly to the primary content of the page, bypassing repetitive navigation.
Quick Reference
- Ensure each page has exactly one
<main>element - Avoid multiple elements with
role='main' - Provides a clear starting point for the page's primary content
Check
Count the number of elements or elements with role='main' on the page to ensure there is exactly one.
Fix
Combine multiple main content areas into a single element or remove the 'role=main' attribute from extra containers.
Explain
Explain how the main landmark acts as a primary navigation target for assistive technologies, and why multiple main areas cause confusion.
Code Review
Review the rendered markup and interactive states that affect Use exactly one main landmark. 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-one-main
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should the agent use this skill?
- When reviewing rendered HTML, interactive components, or design-system patterns related to using exactly one main landmark.
- What does the skill check?
- That a page has exactly one main content region. It checks native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- Why does one main landmark matter?
- It lets assistive technology users land in the right place on a page.
Advanced
- Item type
- skill
- Key
landmark-one-main- Source
- github.com/thedaviddias/front-end-checklist