@surea11y/core 1.5.0 → 1.7.0

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

@@ -0,0 +1,231 @@
+/* SPDX-License-Identifier: MPL-2.0 */
+
+'use strict';
+
+/**
+ * @check landmark-complementary-is-top-level
+ * @atomic true
+ * @summary The complementary landmark must not be nested inside another landmark
+ * @standard Best Practices (no formal WCAG Success Criterion)
+ * @applicability
+ *   Applies whenever the page contains at least one element carrying the
+ *   complementary role: explicit role="complementary", or an <aside> that
+ *   keeps its implicit role (see implementation notes on when it does not).
+ * @expectation
+ *   No complementary candidate has an ancestor that is itself a landmark
+ *   region. Complementary content supports the main content of the page and
+ *   sits beside it; nested inside another landmark it is a section of that
+ *   landmark instead, which is not what landmark navigation announces.
+ * @implementation-notes
+ * - Not WCAG-normative, authored as an advisory, cantTell-capped
+ *   `type: 'manual'` rule, matching its three siblings
+ *   (`landmark-banner-is-top-level`, `landmark-contentinfo-is-top-level`,
+ *   `landmark-main-is-top-level`). Landmark detection and the
+ *   ancestor walk are identical to theirs; only the role being looked for
+ *   differs.
+ * - An unnamed <aside> inside sectioning content has no complementary role
+ *   per HTML-AAM, so it is not a candidate at all: reporting it would name a
+ *   landmark that does not exist. A *named* one keeps the role wherever it
+ *   sits, which is exactly the case worth review -- an <aside aria-label>
+ *   inside <main> really is a complementary landmark nested in another
+ *   landmark. `landmark-unique` and the sibling top-level rules already
+ *   resolve <aside> this way, through the same shared helper.
+ */
+
+const id = 'landmark-complementary-is-top-level';
+
+const meta = {
+  title: 'Complementary landmark must be top-level',
+  description:
+    'Checks that the complementary landmark (role="complementary" or an <aside> that keeps its implicit role) is not nested inside another landmark region.',
+  i18n: {
+    titleKey: 'landmarkComplementaryIsTopLevel_title',
+    descriptionKey: 'landmarkComplementaryIsTopLevel_description'
+  },
+  helpUrl: null,
+  tags: ['best-practice', 'landmarks', 'structure', 'atomic', 'manual'],
+  wcagSc: [],
+  normativeMappings: [],
+  defaultSeverity: 'minor',
+  category: 'operable',
+  type: 'manual',
+  defaultConfidence: 'medium',
+  coverage: {}
+};
+
+function runInPage(ctx) {
+  const { document, root, helpers, rule } = ctx;
+
+  // Declared inside runInPage; see scripts/build-core.js header
+  // ("runInPage MUST be self-contained").
+  function normalizeWs(s) {
+    return String(s || '')
+      .replace(/\s+/g, ' ')
+      .trim();
+  }
+
+  // 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. Sharing it keeps
+  // the title-attribute fallback consistent across the landmark rules.
+  function getAccessibleLandmarkName(el) {
+    try {
+      if (helpers && typeof helpers.getLandmarkNameInfo === 'function') {
+        const info = helpers.getLandmarkNameInfo(el, ctx);
+        if (info && info.present && info.value) return normalizeWs(info.value);
+      }
+    } catch {}
+    return '';
+  }
+
+  function getExplicitRoleToken(el) {
+    const raw = normalizeWs(el.getAttribute && el.getAttribute('role'));
+    if (!raw) return '';
+    return raw.split(/\s+/)[0].toLowerCase();
+  }
+
+  // Delegates to the shared helpers.hasLandmarkScopingAncestor for the
+  // question "does this element sit inside a sectioning-content/<main>
+  // ancestor that suppresses its conditional implicit role": role-aware
+  // (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.
+  function hasSectioningAncestor(el, includeMain) {
+    return helpers && typeof helpers.hasLandmarkScopingAncestor === 'function'
+      ? helpers.hasLandmarkScopingAncestor(el, { includeMain })
+      : false;
+  }
+
+  function getImplicitLandmarkRole(el) {
+    const tag = el.tagName ? el.tagName.toLowerCase() : '';
+    if (tag === 'header') return hasSectioningAncestor(el, true) ? '' : 'banner';
+    if (tag === 'footer') return hasSectioningAncestor(el, true) ? '' : 'contentinfo';
+    if (tag === 'main') return 'main';
+    if (tag === 'nav') return 'navigation';
+    if (tag === 'aside') {
+      // 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' : '';
+    }
+    if (tag === 'section') return getAccessibleLandmarkName(el) ? 'region' : '';
+    if (tag === 'form') return getAccessibleLandmarkName(el) ? 'form' : '';
+    return '';
+  }
+
+  const LANDMARK_ROLES = new Set([
+    'banner',
+    'contentinfo',
+    'main',
+    'navigation',
+    'complementary',
+    'region',
+    'form',
+    'search'
+  ]);
+
+  function getLandmarkRole(el) {
+    if (!el || !el.getAttribute) return '';
+    const explicit = getExplicitRoleToken(el);
+    if (explicit) return LANDMARK_ROLES.has(explicit) ? explicit : '';
+    return getImplicitLandmarkRole(el);
+  }
+
+  // A candidate must actually carry the complementary role. An <aside> that
+  // HTML-AAM strips the role from is not a complementary landmark at all, so
+  // flagging it would report a landmark that does not exist.
+  function isComplementaryCandidate(el) {
+    return getLandmarkRole(el) === 'complementary';
+  }
+
+  function hasLandmarkAncestor(el) {
+    const scopeRoots = Array.isArray(root) ? root : root ? [root] : [];
+    let p = el.parentElement;
+    while (p) {
+      if (getLandmarkRole(p)) return true;
+      // Don't climb past the scanned scope -- see aria-helpers.js's
+      // hasLandmarkScopingAncestor for the same fix and rationale.
+      if (scopeRoots.includes(p)) break;
+      p = p.parentElement;
+    }
+    return false;
+  }
+
+  // queryAllSmart (shadow-DOM-aware) instead of plain document.querySelectorAll -- see
+  // 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 =
+      helpers && typeof helpers.queryAllSmart === 'function'
+        ? helpers.queryAllSmart('header, footer, main, nav, aside, section, form, [role]')
+        : document.querySelectorAll('header, footer, main, nav, aside, section, form, [role]');
+  } catch {
+    nodes = [];
+  }
+
+  const complementaries = [];
+  const seen = new Set();
+  for (const el of nodes) {
+    if (!el || seen.has(el)) continue;
+    seen.add(el);
+    if (!isComplementaryCandidate(el)) continue;
+
+    // An aria-hidden candidate is removed from the accessibility tree
+    // entirely, so it is not part of the landmark structure assistive
+    // technology users navigate and there is no real landmark to call
+    // nested. 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;
+    }
+
+    complementaries.push(el);
+  }
+
+  if (complementaries.length === 0) {
+    return { ruleId: rule.ruleId, outcome: 'notApplicable', severity: 'minor', occurrences: [] };
+  }
+
+  const occurrences = [];
+  for (const el of complementaries) {
+    if (!hasLandmarkAncestor(el)) continue;
+
+    occurrences.push(
+      helpers.reportOccurrence(el, {
+        summary: 'This complementary landmark is nested inside another landmark region.',
+        hint: 'Move the complementary landmark (<aside>/role="complementary") so it is not contained by another landmark; complementary content belongs beside the main content, not inside another region.',
+        i18n: {
+          summaryKey: 'landmarkComplementaryIsTopLevel_summary_cantTell',
+          hintKey: 'landmarkComplementaryIsTopLevel_hint_cantTell',
+          params: {}
+        },
+        data: {
+          details: { reasonCode: 'LANDMARK_COMPLEMENTARY_NOT_TOP_LEVEL' }
+        }
+      })
+    );
+  }
+
+  if (occurrences.length) {
+    return {
+      ruleId: rule.ruleId,
+      outcome: 'cantTell',
+      severity: rule.defaultSeverity || 'minor',
+      occurrences
+    };
+  }
+  return { ruleId: rule.ruleId, outcome: 'notApplicable', severity: 'minor', occurrences: [] };
+}
+
+module.exports = { id, meta, runInPage };

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

@@ -6,25 +6,25 @@
  * @check landmark-contentinfo-is-top-level
  * @atomic true
  * @summary The contentinfo landmark must not be nested inside another landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @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 on
- *   why candidate selection is deliberately unconditional).
+ *   why candidate selection is unconditional on purpose).
  * @expectation
  *   No contentinfo candidate has an ancestor that is itself any landmark
  *   region. A contentinfo nested inside another landmark is not a
  *   top-level, whole-page footer region and confuses landmark-based
  *   navigation for assistive technology users.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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 (this rule mirrors
  *   its structure with contentinfo/footer in place of banner/header).
  * - 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.
+ *   `getLandmarkRole`, same reasoning as landmark-banner-is-top-level.
  */
 
 const id = 'landmark-contentinfo-is-top-level';
@@ -79,7 +79,7 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.hasLandmarkScopingAncestor for the
   // question "does this element sit inside a sectioning-content/<main>
-  // ancestor that suppresses its conditional implicit role" — role-aware
+  // ancestor that suppresses its conditional implicit role": role-aware
   // (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
@@ -98,7 +98,7 @@ 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 — it keeps
+      // 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';
@@ -127,12 +127,12 @@ function runInPage(ctx) {
     return getImplicitLandmarkRole(el);
   }
 
-  // Candidate selection is deliberately NOT the same as getLandmarkRole()
-  // === 'contentinfo' — see the header comment above. A <footer> is
+  // Candidate selection is NOT the same as getLandmarkRole()
+  // === '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
+  // 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) {

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

@@ -6,7 +6,7 @@
  * @check landmark-main-is-top-level
  * @atomic true
  * @summary The main landmark must not be nested inside another landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
  *   Applies whenever the page contains at least one main landmark
  *   (explicit role="main", or an implicit <main> element).
@@ -16,15 +16,15 @@
  *   whole-page main content area and confuses landmark-based navigation
  *   for assistive technology users.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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 (this rule mirrors
  *   its structure with main in place of banner/header).
  * - 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
+ *   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.
  */
@@ -81,7 +81,7 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.hasLandmarkScopingAncestor for the
   // question "does this element sit inside a sectioning-content/<main>
-  // ancestor that suppresses its conditional implicit role" — role-aware
+  // ancestor that suppresses its conditional implicit role": role-aware
   // (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
@@ -100,7 +100,7 @@ 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 — it keeps
+      // 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';

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

@@ -6,19 +6,19 @@
  * @check landmark-no-duplicate-banner
  * @atomic true
  * @summary A page must not have more than one banner landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
  *   Applies whenever the page contains at least one banner landmark
- *   (explicit role="banner", or an implicit, non-nested <header> — see
+ *   (explicit role="banner", or an implicit, non-nested <header>; see
  *   landmark-banner-is-top-level's implementation notes for the
  *   shared landmark-detection model).
  * @expectation
  *   At most one banner landmark exists on the page. Per WAI-ARIA
  *   Authoring Practices, the banner landmark represents site-oriented
- *   content that identifies the page as a whole — having more than one
+ *   content that identifies the page as a whole, so having more than one
  *   is ambiguous for assistive technology users navigating by landmark.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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.
  * - Flags every banner instance (not just the "extra" ones) when more
@@ -81,11 +81,11 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.hasLandmarkScopingAncestor for the
   // question "does this element sit inside a sectioning-content/<main>
-  // ancestor that suppresses its conditional implicit role" — role-aware
+  // ancestor that suppresses its conditional implicit role": role-aware
   // (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 — e.g. an
+  // 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) {

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

@@ -6,18 +6,18 @@
  * @check landmark-no-duplicate-contentinfo
  * @atomic true
  * @summary A page must not have more than one contentinfo landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
  *   Applies whenever the page contains at least one contentinfo landmark
  *   (explicit role="contentinfo", or an implicit, non-nested <footer>).
  * @expectation
- *   At most one contentinfo landmark exists on the page — mirrors
+ *   At most one contentinfo landmark exists on the page, mirroring
  *   landmark-no-duplicate-banner's rationale for contentinfo.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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 —
+ * - Only landmarks actually exposed to assistive technology can collide,
  *   same as the sibling banner/main rules, avoiding hidden-duplicate false
  *   positives.
  */
@@ -74,7 +74,7 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.hasLandmarkScopingAncestor for the
   // question "does this element sit inside a sectioning-content/<main>
-  // ancestor that suppresses its conditional implicit role" — role-aware
+  // ancestor that suppresses its conditional implicit role": role-aware
   // (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
@@ -93,7 +93,7 @@ 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 — it keeps
+      // 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';

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

@@ -6,7 +6,7 @@
  * @check landmark-no-duplicate-main
  * @atomic true
  * @summary A page must not have more than one main landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
  *   Applies whenever the page contains at least one main landmark
  *   (explicit role="main", or an implicit <main>).
@@ -15,7 +15,7 @@
  *   decision from landmark-one-main (that rule flags zero
  *   mains too; this one only flags more than one).
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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.

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

@@ -6,24 +6,24 @@
  * @check landmark-one-main
  * @atomic true
  * @summary The page should have a main landmark
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
- *   Always applicable to any HTML document with a <body> element —
+ *   Always applicable to any HTML document with a <body> element:
  *   "does the page have a main landmark" is a whole-page concern,
  *   matching bypass-blocks-present's pattern of evaluating the
  *   document directly.
  * @expectation
  *   At least one main landmark (role="main" or <main>), exposed to
- *   assistive technology, exists on the page — a page with none gives
+ *   assistive technology, exists on the page. A page with none gives
  *   AT users no landmark to jump straight to for the primary content.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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: 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>`
+ *   `landmark-no-duplicate-main`, already implemented and not
+ *   duplicated here, since a page can legitimately 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/

package/src/checks/manual/landmark-unique-manual.js

@@ -6,20 +6,20 @@
  * @check landmark-unique
  * @atomic true
  * @summary Landmarks sharing the same role must have unique accessible names
- * @standard Best Practices (no formal WCAG Success Criterion — see ROADMAP.md Tier 1b)
+ * @standard Best Practices (no formal WCAG Success Criterion)
  * @applicability
  *   Applies whenever two or more landmark regions on the page share the
  *   same landmark role (banner, contentinfo, main, navigation,
- *   complementary, region, form, or search — see implementation notes
+ *   complementary, region, form, or search; see implementation notes
  *   for the detection model).
  * @expectation
  *   Among landmarks sharing a role, each has a distinct accessible name
- *   (via aria-label/aria-labelledby — landmarks are not named from
+ *   (via aria-label/aria-labelledby; landmarks are not named from
  *   content). Two same-role landmarks with the same name (including two
  *   both left unnamed) are indistinguishable to assistive technology
  *   users navigating by landmark.
  * @implementation-notes
- * - Not WCAG-normative — authored as an advisory, cantTell-capped
+ * - 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 and the landmark-
  *   detection model (HTML-AAM implicit-role mapping + explicit role
@@ -80,18 +80,18 @@ function runInPage(ctx) {
 
   // Delegates to the shared helpers.hasLandmarkScopingAncestor (role-aware:
   // an ancestor's bare TAG only counts when it carries no role attribute at
-  // all; an explicit role="dialog"-style override no longer suppresses —
+  // all; an explicit role="dialog"-style override no longer suppresses;
   // see that function's header comment in src/core/aria-helpers.js), using
   // two distinct ancestor scopes rather than one shared list: <header>/
   // <footer> use "sectioning content PLUS <main>" (includeMain: true) to
   // decide banner/contentinfo suppression, but <aside> uses PLAIN
-  // sectioning content only — NOT main (includeMain: false) — to decide
+  // sectioning content only, not main (includeMain: false), to decide
   // complementary suppression. A single shared sectioning-ancestors set
   // that includes 'main' is correct for header/footer but wrong for aside:
   // e.g. two unnamed <aside> elements that are direct children of <main>
   // would have their implicit "complementary" role incorrectly suppressed,
   // hiding a real duplicate-landmark violation. The role-aware half matters
-  // too: e.g. an <aside role="dialog"> containing its own <header> —
+  // too: take an <aside role="dialog"> containing its own <header>.
   // role="dialog" isn't one of the four scoping roles, so the nested
   // <header> keeps "banner" per spec, but a tag-only (non-role-aware)
   // check would unconditionally suppress it just because the ancestor TAG
@@ -110,7 +110,7 @@ function runInPage(ctx) {
     if (tag === 'nav') return 'navigation';
     if (tag === 'aside') {
       // An <aside> is suppressed by a sectioning-content ancestor ONLY
-      // when it also has no accessible name — a named <aside> is never
+      // when it also has no accessible name. A named <aside> is never
       // suppressed, even when nested.
       if (!hasSectioningAncestor(el, false)) return 'complementary';
       return getAccessibleLandmarkName(el) ? 'complementary' : '';
@@ -137,7 +137,7 @@ function runInPage(ctx) {
     if (explicit) {
       if (!LANDMARK_ROLES.has(explicit)) return '';
       // <form>/<section> only count as landmarks when they have an
-      // accessible name — a property of the ELEMENT, not of how the role
+      // accessible name, a property of the ELEMENT, not of how the role
       // got there. This applies whether the role is implicit (already
       // handled in getImplicitLandmarkRole below) or explicit. Per the W3C
       // ARIA-in-HTML spec ("a form is not exposed as a landmark region