Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use exactly one main landmark. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
This skill checks whether a page has exactly one main landmark: the marker identifying its primary content. It counts <main> elements and elements with role='main' in rendered HTML, then identifies missing or duplicate main regions. Where multiple primary regions exist, it explains how to combine them into one <main> element or remove role='main' from extra containers.
Use it when reviewing page templates or shared layouts. It also helps check whether combining several components has created duplicate main regions. A clearly identified main region gives keyboard and screen-reader users a target for moving directly to the page’s content while skipping navigation that appears repeatedly.
<main> elements and elements with role='main' on this page, and confirm that there is exactly one main region.”There are no special notes.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
A single main landmark allows keyboard and screen reader users to jump directly to the primary content of the page, bypassing repetitive navigation.
<main> elementrole='main'Count the number of <main> elements or elements with role='main' on the page to ensure there is exactly one.
Combine multiple main content areas into a single <main> element or remove the 'role=main' attribute from extra containers.
Explain how the main landmark acts as a primary navigation target for assistive technologies, and why multiple main areas cause confusion.
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/rules/accessibility/landmark-one-main
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.