Review page landmarks, the named regions screen reader users navigate between. The skill checks semantic HTML elements, a single main content region, and labels for repeated region types, then identifies markup changes and ways to verify them.
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.
This skill reviews landmarks, the major regions of a page that screen reader users can navigate between. It helps organize HTML so users can reach the section they need. The review checks how <header>, <nav>, <main>, and <footer> are used and suggests replacing generic <div> containers with elements that match their purpose. It also checks that the page has one <main> region and that multiple regions of the same type are distinguished with aria-label.
Use it when reviewing accessibility in pages with complex layouts or in shared page templates. It helps when you need to communicate the location of the main content or menus to assistive technology, or make multiple navigation regions distinguishable when read aloud. Working from rendered HTML, it identifies problematic elements and labels and describes how to verify changes using browser accessibility tools or assistive technology.
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.
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/rules/accessibility/landmark-regions
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.