@piercebarney/whs-eleventy 2026.10.6 → 2026.10.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@piercebarney/whs-eleventy",
-  "version": "2026.10.6",
+  "version": "2026.10.7",
   "description": "The web house style's Eleventy + Netlify tooling — the compliance sweep, the infra doctor, the link/CSP integrity check, and the a11y scan, shared by every project on the stack.",
   "bin": {
     "whs": "cli.js"

package/standard/CHANGELOG.md

@@ -21,6 +21,43 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 
 ---
 
+## 2026-10-07 [breaking]
+
+### core: a11y
+
+`core.md#a11y`'s Contract never named a WCAG version/level as its
+conformance target — only "WCAG AA" for contrast. It now declares **WCAG 2.1
+Level AA** explicitly as the target, anchored to US law (the ADA Title II
+rule and US web-accessibility litigation/settlements reference WCAG 2.1 AA;
+Section 508's WCAG 2.0 AA is already covered by it) rather than WCAG 2.2 AA
+— the upgrade trigger to 2.2 AA is recorded, not scheduled, for once US rules
+reference it. **Breaking:** a project that was previously compliant by
+meeting the checklist plus passing the automated scan must now conform to
+all of WCAG 2.1 AA, including criteria the checklist and scan don't
+individually name (e.g. captions, reflow, keyboard operability everywhere)
+— a real added requirement, not just a clarification of an already-met bar.
+No tooling change: Eleventy's `whs a11y` scan already runs `wcag2a`/
+`wcag2aa`/`wcag21a`/`wcag21aa` — it already matched this target. SvelteKit's
+and Phoenix's scan gaps (no automated a11y tooling yet) are pre-existing and
+unrelated to this change. Decided by the owner in
+`feedback/2026-09-26-external-standards-survey.md` ("Decisions (2026-09-26)"
+item 1); see that file for the full WCAG-version rationale, including why
+2.1 and not 2.2.
+
+### core: styling
+
+The contrast line in `#styling` now also says "WCAG 2.1 AA" (was "WCAG AA"),
+matching the version now named in `#a11y`.
+
+### stacks/eleventy-netlify.md, stacks/phoenix.md, stacks/sveltekit-netlify.md
+
+Each of `stacks/eleventy-netlify.md`, `stacks/phoenix.md`, and
+`stacks/sveltekit-netlify.md`'s `#a11y` Core-contract pointer line now
+mentions WCAG 2.1 AA alongside the existing checklist/scan pointer — no
+change to any stack's own mechanism.
+
+---
+
 ## 2026-10-06 [breaking]
 
 ### packages/whs-eleventy

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-10-06 · **Status:** active
+**Version:** 2026-10-07 · **Status:** active
 
 This is the stack-agnostic contract every web project follows, regardless of
 framework, host, or CSS system. It says **what** must be true, with concrete
@@ -244,7 +244,7 @@ contrast-correct at the token level.
 - **Strict-CSP-safe:** no `style-src 'unsafe-inline'`, no inline `style=`
   attributes in templates, no per-page `<style>` blocks. Utility-class systems
   (Tailwind) are fine; inline style strings are not.
-- Contrast meets WCAG AA. When a pair fails, fix the **token**, not the usage.
+- Contrast meets WCAG 2.1 AA. When a pair fails, fix the **token**, not the usage.
 - Theme is applied via a data attribute set before first paint (`#theme`).
 - A second stylesheet only for a genuinely separable widget, justified in a
   comment.
@@ -834,8 +834,11 @@ states.
 
 ## a11y — Accessibility checklist
 
-**Contract.** Every page meets the checklist below. An automated a11y scan over
-every page runs in the gate — and is understood to catch regressions, not
+**Contract.** Every page conforms to **WCAG 2.1 Level AA** — the level US
+accessibility law references (the ADA Title II rule; Section 508's WCAG 2.0 AA
+is covered by it). The checklist below is the house's concrete mechanism for
+the parts of AA most often missed, not the whole of it. An automated a11y scan
+over every page runs in the gate — and is understood to catch regressions, not
 everything.
 
 **Specs.**
@@ -858,7 +861,7 @@ everything.
   keyboard button — don't re-bind Enter/Space or add `role`/`tabindex`.
 - **Icons:** decorative → `aria-hidden="true"`; meaningful → `<title>` in the
   SVG or `aria-label` on the control.
-- **Contrast** meets WCAG AA; fix failures at the token (`#brand-source`), not
+- **Contrast** meets WCAG 2.1 AA; fix failures at the token (`#brand-source`), not
   with a one-off override.
 - **Focus visibility:** a visible focus ring on every interactive element; if
   you override the default, keep one.
@@ -1467,7 +1470,7 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
 - production-url: https://example.com
 - content-type: tool           # tool | article  (article => feeds)
 - publishing-rate: ~5 pages/week
-- standard-version: 2026-10-06  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-10-07  # recommended — enables standard-version drift tracking (#compliance)
 ```
 
 If the section is absent, the assistant's first action is to run the flow above