v1.4.0 - WCAG 2.2 AA

What's New in v1.4.0

WCAG 2.2 AA Scanning Mode

AllyCat now supports WCAG 2.2 AA as a selectable standard — pick it in allycat init or set it directly in your config.

{
  "selectedStandard": "wcag-22-aa"
}

Uses axe-core's full WCAG 2.2 tag set. In axe-core v4.11.1 this adds one additional automated rule over WCAG 2.1 AA: target-size (SC 2.5.8 — minimum 24×24px touch target). Recommended for new projects targeting the 2025+ standard.

---

Bug Fix — Init Summary Display

The allycat init confirmation screen now shows the correct human-readable standard name instead of the raw config value.

┌─────────────────┬────────────┬────────────────────────────┐
│ Standard picked │   Before   │           After            │
├─────────────────┼────────────┼────────────────────────────┤
│ WCAG 2.1 AA     │ WCAG-AA    │ WCAG 2.1 AA                │
├─────────────────┼────────────┼────────────────────────────┤
│ WCAG 2.2 AA     │ WCAG-22-AA │ WCAG 2.2 AA                │
├─────────────────┼────────────┼────────────────────────────┤
│ WCAG AAA        │ WCAG-AAA   │ WCAG AAA (automated rules) │
└─────────────────┴────────────┴────────────────────────────┘

---

Bug Fix — Ghost axe-core Tag Removed

The WCAG AAA tag set included wcag21aaa, a tag that does not exist in axe-core v4.11.1. It was silently contributing zero rules. Removed.

---

AAA Standard Relabeled

AAA mode is now labeled "WCAG AAA (automated rules)" everywhere — init wizard, reports, and help text. The previous label ("WCAG 2.1 AAA") overstated coverage. Full AAA conformance always requires a manual audit alongside automated tooling.

---

Upgrade Notes

• Run allycat init to select WCAG 2.2 AA, or add "selectedStandard": "wcag-22-aa" to your existing allycat.config.json.
• No breaking changes. All existing flags and config fields work as before.

---

Full changelog→ CHANGELOG.md