{
  "componentId": "badge",
  "componentName": "Badge",
  "lastReviewed": "2026-05-05",
  "keyboardWalk": [
    {
      "keys": "Tab (badge inside a focusable host)",
      "expected": "Focus enters the host element (button, link, list-item). Badge is not in the tab order — it is presentational metadata about the host. Subsequent Tab leaves the host; the badge is not visited as a separate stop."
    },
    {
      "keys": "Tab (interactive badge, rare)",
      "expected": "When the consumer promotes Badge to interactive (uncommon), the badge participates in the tab order as a single stop and Enter activates it. Hit target ≥ 24×24 px per WCAG 2.5.8."
    }
  ],
  "announcements": [
    {
      "trigger": "SR enters a host with a badge child",
      "expected": "SR reads the host's accessible name followed by the badge's accessible name in DOM order. Decorative dot badges with `role=\"presentation\"` are skipped; iconic badges with `aria-label` read their label."
    },
    {
      "trigger": "Live count updates",
      "expected": "SR announces the new count value via the polite live region. Throttled by the implementation to avoid flooding SR output during rapid increments."
    }
  ],
  "axeRules": [
    "aria-allowed-attr",
    "aria-valid-attr-value",
    "color-contrast",
    "role-img-alt"
  ],
  "_about": "Per-component a11y-acceptance data shaped for direct ingestion into Playwright + @axe-core/playwright or Jest + jest-axe.\n\nSuggested wiring:\n- axeRules → pass to AxeBuilder.options({ runOnly: { type: \"rule\", values: axeRules } }) so the run targets only the rules the canon has pinned for this component (other rules can run in your global pass).\n- keyboardWalk → iterate the entries; each `keys` is a human-readable sequence (e.g. \"Tab → Tab → Esc\"). Translate to page.keyboard.press calls and assert `expected` against the result (focused element, aria-state, visible text, etc.).\n- announcements → assert text content of any aria-live region or capture the accessibility tree at the trigger moment and match against `expected`.\n\nEmpty sub-arrays mean the canon does not yet pin behaviour for that axis on this component, not that none is required."
}