@surea11y/core 1.3.0 → 1.4.1

package/src/checks/manual/landmark-contentinfo-is-top-level-manual.js

@@ -1,15 +1,17 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-contentinfo-is-top-level
  * @atomic true
  * @summary The contentinfo landmark must not be nested inside another landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Applies whenever the page contains at least one contentinfo
  *   candidate: explicit role="contentinfo", OR a <footer> with NO role
- *   attribute at all (regardless of nesting — see implementation notes'
- *   2026-08-01 fix).
+ *   attribute at all, regardless of nesting (see implementation notes on
+ *   why candidate selection is deliberately unconditional).
  * @expectation
  *   No contentinfo candidate has an ancestor that is itself any landmark
  *   region. A contentinfo nested inside another landmark is not a
@@ -20,13 +22,9 @@
  *   `type: 'manual'` rule; see landmark-banner-is-top-level's
  *   header comment for the shared rationale/precedent (this rule mirrors
  *   its structure with contentinfo/footer in place of banner/header).
- * - **Fixed 2026-08-01, same self-defeating applicability bug as
- *   landmark-banner-is-top-level (see that file's header comment for the
- *   full root cause and the TurboTax evidence) — candidate selection
- *   (`isContentinfoCandidate` below) now matches a widely-used reference
- *   engine's unconditional `footer:not([role]), [role=contentinfo]`
- *   selector shape instead of reusing the sectioning-ancestor
- *   suppression that the violation check itself depends on.
+ * - Candidate selection (`isContentinfoCandidate`) requires the element to
+ *   really carry the contentinfo role, via the suppression-aware
+ *   `getLandmarkRole` — same reasoning as landmark-banner-is-top-level.
  */
 
 const id = 'landmark-contentinfo-is-top-level';
@@ -61,9 +59,8 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.getLandmarkNameInfo (aria-label -> aria-labelledby, via the
   // target's own accessible name, not raw textContent -> title attribute fallback) rather than a
-  // local copy -- see that function's header comment in src/core/dom-helpers.js for the real bug
-  // (missing title fallback) this replaced across all 7 landmark rule files that had their own
-  // copy of this logic.
+  // local copy -- see that function's header comment in src/core/dom-helpers.js. Sharing it keeps
+  // the title-attribute fallback consistent across the landmark rules.
   function getAccessibleLandmarkName(el) {
     try {
       if (helpers && typeof helpers.getLandmarkNameInfo === 'function') {
@@ -86,10 +83,8 @@ function runInPage(ctx) {
   // (an ancestor's bare TAG only counts when it carries no role attribute
   // at all; an explicit role="dialog"-style override no longer suppresses)
   // rather than a local tag-only copy. See that function's header comment
-  // in src/core/aria-helpers.js for the full algorithm and the real page
-  // (handsontable.com's docs-assistant side panel, an
-  // <aside role="dialog"> containing its own <header>) that surfaced this
-  // rule's own former tag-only copy as a false negative.
+  // in src/core/aria-helpers.js for the full algorithm. Example: an
+  // <aside role="dialog"> containing its own <header>.
   function hasSectioningAncestor(el, includeMain) {
     return helpers && typeof helpers.hasLandmarkScopingAncestor === 'function'
       ? helpers.hasLandmarkScopingAncestor(el, { includeMain })
@@ -103,11 +98,9 @@ function runInPage(ctx) {
     if (tag === 'main') return 'main';
     if (tag === 'nav') return 'navigation';
     if (tag === 'aside') {
-      // A named <aside> is never suppressed, even when nested — matches
-      // landmark-unique's own verified-against-reference-engine precedent
-      // (that engine's real `aside` implicit-role function keeps
-      // "complementary" when the element has an accessible name, even
-      // inside sectioning content); propagated here for consistency.
+      // A named <aside> is never suppressed, even when nested — it keeps
+      // "complementary" when it has an accessible name, even inside
+      // sectioning content. Matches landmark-unique's precedent.
       if (!hasSectioningAncestor(el, false)) return 'complementary';
       return getAccessibleLandmarkName(el) ? 'complementary' : '';
     }
@@ -135,15 +128,15 @@ function runInPage(ctx) {
   }
 
   // Candidate selection is deliberately NOT the same as getLandmarkRole()
-  // === 'contentinfo' — see the 2026-08-01 fix note above. A <footer> is
+  // === 'contentinfo' — see the header comment above. A <footer> is
   // a candidate purely by tag + absence of any role attribute, independent
   // of whether sectioning-ancestor nesting would currently suppress its
   // implicit role; an explicit role="contentinfo" is always a candidate too.
+  // A candidate must actually have the contentinfo role — a <footer> inside
+  // article/aside/main/nav/section is not one, so flagging it as nested
+  // would report a landmark that does not exist.
   function isContentinfoCandidate(el) {
-    if (!el || !el.getAttribute) return false;
-    const explicit = getExplicitRoleToken(el);
-    if (explicit) return explicit === 'contentinfo';
-    return !!(el.tagName && el.tagName.toLowerCase() === 'footer');
+    return getLandmarkRole(el) === 'contentinfo';
   }
 
   function hasLandmarkAncestor(el) {
@@ -160,9 +153,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =
@@ -178,7 +170,28 @@ function runInPage(ctx) {
   for (const el of nodes) {
     if (!el || seen.has(el)) continue;
     seen.add(el);
-    if (isContentinfoCandidate(el)) contentinfos.push(el);
+    if (!isContentinfoCandidate(el)) continue;
+
+    // An aria-hidden contentinfo candidate is removed from the
+    // accessibility tree entirely -- it isn't part of the landmark
+    // structure assistive technology users navigate at all, so it
+    // shouldn't be flagged as "nested inside another landmark" (there's
+    // no real landmark there to begin with, from AT's perspective).
+    // queryAllSmart's default hidden-content policy only excludes "hard"
+    // CSS-based hiding (display:none, etc.), not the softer aria-hidden
+    // exclusion, so this needs its own check.
+    if (helpers && typeof helpers.isAccTreeEligible === 'function') {
+      const elig = (() => {
+        try {
+          return helpers.isAccTreeEligible(el, ctx);
+        } catch {
+          return { eligible: true, reasons: [] };
+        }
+      })();
+      if (elig && elig.eligible === false) continue;
+    }
+
+    contentinfos.push(el);
   }
 
   if (contentinfos.length === 0) {

package/src/checks/manual/landmark-main-is-top-level-manual.js

@@ -1,10 +1,12 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-main-is-top-level
  * @atomic true
  * @summary The main landmark must not be nested inside another landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Applies whenever the page contains at least one main landmark
  *   (explicit role="main", or an implicit <main> element).
@@ -18,13 +20,13 @@
  *   `type: 'manual'` rule; see landmark-banner-is-top-level's
  *   header comment for the shared rationale/precedent (this rule mirrors
  *   its structure with main in place of banner/header).
- * - Did NOT need the 2026-08-01 fix applied to
- *   landmark-banner-is-top-level/landmark-contentinfo-is-top-level (see
- *   that file's header comment): `<main>`'s implicit role is
- *   unconditional per HTML-AAM — unlike `<header>`/`<footer>`, nesting
- *   never suppresses it — so `getImplicitLandmarkRole`'s `main` branch
- *   was never subject to the same self-defeating candidate-selection
- *   bug. Confirmed by inspection, not just by absence of a bug report.
+ * - Unlike landmark-banner-is-top-level/landmark-contentinfo-is-top-level
+ *   (see that file's header comment), candidate selection here doesn't
+ *   need to be unconditional: `<main>`'s implicit role is unconditional
+ *   per HTML-AAM — unlike `<header>`/`<footer>`, nesting never suppresses
+ *   it — so `getImplicitLandmarkRole`'s `main` branch is never subject to
+ *   the self-defeating candidate-selection problem those two rules guard
+ *   against.
  */
 
 const id = 'landmark-main-is-top-level';
@@ -59,9 +61,8 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.getLandmarkNameInfo (aria-label -> aria-labelledby, via the
   // target's own accessible name, not raw textContent -> title attribute fallback) rather than a
-  // local copy -- see that function's header comment in src/core/dom-helpers.js for the real bug
-  // (missing title fallback) this replaced across all 7 landmark rule files that had their own
-  // copy of this logic.
+  // local copy -- see that function's header comment in src/core/dom-helpers.js. Sharing it keeps
+  // the title-attribute fallback consistent across the landmark rules.
   function getAccessibleLandmarkName(el) {
     try {
       if (helpers && typeof helpers.getLandmarkNameInfo === 'function') {
@@ -84,10 +85,8 @@ function runInPage(ctx) {
   // (an ancestor's bare TAG only counts when it carries no role attribute
   // at all; an explicit role="dialog"-style override no longer suppresses)
   // rather than a local tag-only copy. See that function's header comment
-  // in src/core/aria-helpers.js for the full algorithm and the real page
-  // (handsontable.com's docs-assistant side panel, an
-  // <aside role="dialog"> containing its own <header>) that surfaced this
-  // rule's own former tag-only copy as a false negative.
+  // in src/core/aria-helpers.js for the full algorithm. Example: an
+  // <aside role="dialog"> containing its own <header>.
   function hasSectioningAncestor(el, includeMain) {
     return helpers && typeof helpers.hasLandmarkScopingAncestor === 'function'
       ? helpers.hasLandmarkScopingAncestor(el, { includeMain })
@@ -101,11 +100,9 @@ function runInPage(ctx) {
     if (tag === 'main') return 'main';
     if (tag === 'nav') return 'navigation';
     if (tag === 'aside') {
-      // A named <aside> is never suppressed, even when nested — matches
-      // landmark-unique's own verified-against-reference-engine precedent
-      // (that engine's real `aside` implicit-role function keeps
-      // "complementary" when the element has an accessible name, even
-      // inside sectioning content); propagated here for consistency.
+      // A named <aside> is never suppressed, even when nested — it keeps
+      // "complementary" when it has an accessible name, even inside
+      // sectioning content. Matches landmark-unique's precedent.
       if (!hasSectioningAncestor(el, false)) return 'complementary';
       return getAccessibleLandmarkName(el) ? 'complementary' : '';
     }
@@ -146,9 +143,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =
@@ -164,7 +160,28 @@ function runInPage(ctx) {
   for (const el of nodes) {
     if (!el || seen.has(el)) continue;
     seen.add(el);
-    if (getLandmarkRole(el) === 'main') mains.push(el);
+    if (getLandmarkRole(el) !== 'main') continue;
+
+    // An aria-hidden main candidate is removed from the accessibility
+    // tree entirely -- it isn't part of the landmark structure assistive
+    // technology users navigate at all, so it shouldn't be flagged as
+    // "nested inside another landmark" (there's no real landmark there to
+    // begin with, from AT's perspective). queryAllSmart's default hidden-
+    // content policy only excludes "hard" CSS-based hiding (display:none,
+    // etc.), not the softer aria-hidden exclusion, so this needs its own
+    // check.
+    if (helpers && typeof helpers.isAccTreeEligible === 'function') {
+      const elig = (() => {
+        try {
+          return helpers.isAccTreeEligible(el, ctx);
+        } catch {
+          return { eligible: true, reasons: [] };
+        }
+      })();
+      if (elig && elig.eligible === false) continue;
+    }
+
+    mains.push(el);
   }
 
   if (mains.length === 0) {

package/src/checks/manual/landmark-no-duplicate-banner-manual.js

@@ -1,10 +1,12 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-no-duplicate-banner
  * @atomic true
  * @summary A page must not have more than one banner landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Applies whenever the page contains at least one banner landmark
  *   (explicit role="banner", or an implicit, non-nested <header> — see
@@ -21,14 +23,11 @@
  *   header comment for the shared rationale/precedent.
  * - Flags every banner instance (not just the "extra" ones) when more
  *   than one exists, since which instance is "correct" is ambiguous.
- * - Only landmarks actually exposed to assistive technology can collide —
- *   matches a widely-used reference engine's own `page-no-duplicate` check (confirmed by reading
- *   its source directly: `query_selector_all_filter_default(..., elm =>
- *   _isVisibleToScreenReaders(elm))`). Without this, a responsive layout
- *   rendering both a visible and a CSS-hidden duplicate `<header>` (found
- *   on a real site — Trello's homepage, a desktop/mobile header pair) was
- *   wrongly flagged as a duplicate landmark; the hidden copy is never
- *   actually reachable by AT.
+ * - Only landmarks actually exposed to assistive technology can collide.
+ *   Without this, a responsive layout rendering both a visible and a
+ *   CSS-hidden duplicate `<header>` (a desktop/mobile header pair) is
+ *   flagged as a duplicate landmark even though the hidden copy is never
+ *   reachable by AT.
  */
 
 const id = 'landmark-no-duplicate-banner';
@@ -63,9 +62,7 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.getLandmarkNameInfo (aria-label -> aria-labelledby, via the
   // target's own accessible name, not raw textContent -> title attribute fallback) rather than a
-  // local copy -- see that function's header comment in src/core/dom-helpers.js for the real bug
-  // (missing title fallback) this replaced across all 7 landmark rule files that had their own
-  // copy of this logic.
+  // local copy -- see that function's header comment in src/core/dom-helpers.js.
   function getAccessibleLandmarkName(el) {
     try {
       if (helpers && typeof helpers.getLandmarkNameInfo === 'function') {
@@ -88,10 +85,9 @@ function runInPage(ctx) {
   // (an ancestor's bare TAG only counts when it carries no role attribute
   // at all; an explicit role="dialog"-style override no longer suppresses)
   // rather than a local tag-only copy. See that function's header comment
-  // in src/core/aria-helpers.js for the full algorithm and the real page
-  // (handsontable.com's docs-assistant side panel, an
-  // <aside role="dialog"> containing its own <header>) that surfaced this
-  // rule's own former tag-only copy as a false negative.
+  // in src/core/aria-helpers.js for the full algorithm — e.g. an
+  // <aside role="dialog"> containing its own <header>, where the <header>
+  // keeps its banner role.
   function hasSectioningAncestor(el, includeMain) {
     return helpers && typeof helpers.hasLandmarkScopingAncestor === 'function'
       ? helpers.hasLandmarkScopingAncestor(el, { includeMain })
@@ -105,11 +101,9 @@ function runInPage(ctx) {
     if (tag === 'main') return 'main';
     if (tag === 'nav') return 'navigation';
     if (tag === 'aside') {
-      // A named <aside> is never suppressed, even when nested — matches
-      // landmark-unique's own verified-against-reference-engine precedent
-      // (that engine's real `aside` implicit-role function keeps
+      // A named <aside> is never suppressed, even when nested: keeps
       // "complementary" when the element has an accessible name, even
-      // inside sectioning content); propagated here for consistency.
+      // inside sectioning content. See landmark-unique-manual.js.
       if (!hasSectioningAncestor(el, false)) return 'complementary';
       return getAccessibleLandmarkName(el) ? 'complementary' : '';
     }
@@ -137,9 +131,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =

package/src/checks/manual/landmark-no-duplicate-contentinfo-manual.js

@@ -1,10 +1,12 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-no-duplicate-contentinfo
  * @atomic true
  * @summary A page must not have more than one contentinfo landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Applies whenever the page contains at least one contentinfo landmark
  *   (explicit role="contentinfo", or an implicit, non-nested <footer>).
@@ -16,11 +18,8 @@
  *   `type: 'manual'` rule; see landmark-banner-is-top-level's
  *   header comment for the shared rationale/precedent.
  * - Only landmarks actually exposed to assistive technology can collide —
- *   matches a widely-used reference engine's own `page-no-duplicate` check (confirmed by reading
- *   its source directly: `query_selector_all_filter_default(..., elm =>
- *   _isVisibleToScreenReaders(elm))`) — same fix applied to the sibling
- *   banner/main rules after finding real hidden-duplicate false positives
- *   on Trello and Zoom.
+ *   same as the sibling banner/main rules, avoiding hidden-duplicate false
+ *   positives.
  */
 
 const id = 'landmark-no-duplicate-contentinfo';
@@ -55,9 +54,8 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.getLandmarkNameInfo (aria-label -> aria-labelledby, via the
   // target's own accessible name, not raw textContent -> title attribute fallback) rather than a
-  // local copy -- see that function's header comment in src/core/dom-helpers.js for the real bug
-  // (missing title fallback) this replaced across all 7 landmark rule files that had their own
-  // copy of this logic.
+  // local copy -- see that function's header comment in src/core/dom-helpers.js. Sharing it keeps
+  // the title-attribute fallback consistent across the landmark rules.
   function getAccessibleLandmarkName(el) {
     try {
       if (helpers && typeof helpers.getLandmarkNameInfo === 'function') {
@@ -80,10 +78,8 @@ function runInPage(ctx) {
   // (an ancestor's bare TAG only counts when it carries no role attribute
   // at all; an explicit role="dialog"-style override no longer suppresses)
   // rather than a local tag-only copy. See that function's header comment
-  // in src/core/aria-helpers.js for the full algorithm and the real page
-  // (handsontable.com's docs-assistant side panel, an
-  // <aside role="dialog"> containing its own <header>) that surfaced this
-  // rule's own former tag-only copy as a false negative.
+  // in src/core/aria-helpers.js for the full algorithm. Example: an
+  // <aside role="dialog"> containing its own <header>.
   function hasSectioningAncestor(el, includeMain) {
     return helpers && typeof helpers.hasLandmarkScopingAncestor === 'function'
       ? helpers.hasLandmarkScopingAncestor(el, { includeMain })
@@ -97,11 +93,9 @@ function runInPage(ctx) {
     if (tag === 'main') return 'main';
     if (tag === 'nav') return 'navigation';
     if (tag === 'aside') {
-      // A named <aside> is never suppressed, even when nested — matches
-      // landmark-unique's own verified-against-reference-engine precedent
-      // (that engine's real `aside` implicit-role function keeps
-      // "complementary" when the element has an accessible name, even
-      // inside sectioning content); propagated here for consistency.
+      // A named <aside> is never suppressed, even when nested — it keeps
+      // "complementary" when it has an accessible name, even inside
+      // sectioning content. Matches landmark-unique's precedent.
       if (!hasSectioningAncestor(el, false)) return 'complementary';
       return getAccessibleLandmarkName(el) ? 'complementary' : '';
     }
@@ -129,9 +123,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =

package/src/checks/manual/landmark-no-duplicate-main-manual.js

@@ -1,29 +1,27 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-no-duplicate-main
  * @atomic true
  * @summary A page must not have more than one main landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Applies whenever the page contains at least one main landmark
  *   (explicit role="main", or an implicit <main>).
  * @expectation
  *   At most one main landmark exists on the page. Distinct, atomic
  *   decision from landmark-one-main (that rule flags zero
- *   mains too; this one only flags more than one) — matches a widely-used
- *   reference engine shipping both as separate rules with some overlap by design.
+ *   mains too; this one only flags more than one).
  * @implementation-notes
  * - Not WCAG-normative — authored as an advisory, cantTell-capped
  *   `type: 'manual'` rule; see landmark-banner-is-top-level's
  *   header comment for the shared rationale/precedent.
- * - Only landmarks actually exposed to assistive technology can collide —
- *   matches a widely-used reference engine's own `page-no-duplicate` check (confirmed by reading
- *   its source directly: `query_selector_all_filter_default(..., elm =>
- *   _isVisibleToScreenReaders(elm))`). Without this, a responsive layout
- *   rendering both a visible and a CSS-hidden duplicate `<main>` (found on
- *   a real site — Zoom's homepage) was wrongly flagged as a duplicate
- *   landmark; the hidden copy is never actually reachable by AT.
+ * - Only landmarks actually exposed to assistive technology can collide.
+ *   Without this, a responsive layout rendering both a visible and a
+ *   CSS-hidden duplicate `<main>` is flagged as a duplicate landmark even
+ *   though the hidden copy is never reachable by AT.
  */
 
 const id = 'landmark-no-duplicate-main';
@@ -70,9 +68,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =

package/src/checks/manual/landmark-one-main-manual.js

@@ -1,10 +1,12 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
 'use strict';
 
 /**
  * @check landmark-one-main
  * @atomic true
  * @summary The page should have a main landmark
- * @standard Best Practices (a widely-used reference engine's classification; no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
  * @applicability
  *   Always applicable to any HTML document with a <body> element —
  *   "does the page have a main landmark" is a whole-page concern,
@@ -18,27 +20,15 @@
  * - Not WCAG-normative — authored as an advisory, cantTell-capped
  *   `type: 'manual'` rule; see landmark-banner-is-top-level's
  *   header comment for the shared rationale/precedent.
- * - Presence-only, matching a widely-used reference engine's real
- *   `landmark-one-main` scope exactly (confirmed 2026-07-22 by reading that
- *   engine's source directly: its `page-has-main` check is a plain
- *   descendant-exists test, `has-descendant-evaluate` — it does NOT flag
- *   more than one). This rule previously ALSO flagged "more than one main,"
- *   which was both a real scope mismatch against that reference engine (it
- *   ships that as a fully separate rule, `landmark-no-duplicate-main` /
- *   `page-no-duplicate-main`, already correctly implemented here as
- *   `landmark-no-duplicate-main`) and missing that sibling rule's
- *   accessibility-tree visibility filter, so it double-flagged cases the
- *   sibling rule already handles correctly — found via a real page
- *   (2026-07-22, live-DOM corpus): Resy's and DuckDuckGo's homepages each
- *   genuinely have two visible `<main>` elements, which that reference
- *   engine's `landmark-one-main` doesn't flag at all (out of its scope) but
- *   this rule wrongly did, disagreeing with it for a
- *   reason that wasn't a real coverage gap on either side — just a
- *   redundant, incorrectly-scoped extra branch here.
+ * - Presence-only: a plain descendant-exists test. It does NOT flag more
+ *   than one main. "More than one main" is a separate rule,
+ *   `landmark-no-duplicate-main`, already implemented — deliberately not
+ *   duplicated here, since a page can genuinely have two visible `<main>`
+ *   elements, which is out of scope for "does a main landmark exist," not
+ *   a violation this rule should report.
  * - Filters candidates through `isAccTreeEligible` (hidden/aria-hidden/
  *   display:none/inert elements don't count as "a main landmark exists"),
- *   matching `landmark-no-duplicate-main`'s own precedent and
- *   that reference engine's own accessibility-tree-scoped matching.
+ *   matching `landmark-no-duplicate-main`'s own precedent.
  */
 
 const id = 'landmark-one-main';
@@ -106,9 +96,8 @@ function runInPage(ctx) {
   }
 
   // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
-  // landmark-unique-manual.js's header comment for the real page (Airtable, 2026-07-23)
-  // that surfaced this gap: a third-party shadow-DOM-hosted widget's own landmark is
-  // invisible to a light-DOM-only query.
+  // landmark-unique-manual.js's header comment. A third-party shadow-DOM-hosted
+  // widget's own landmark is invisible to a light-DOM-only query.
   let nodes;
   try {
     nodes =