|
| 1 | +# Accessibility adoption evidence |
| 2 | + |
| 3 | +Date: 2026-09-07 |
| 4 | + |
| 5 | +## Action and policy identity |
| 6 | + |
| 7 | +The three required accessibility scans use A11y Audit v3.1.0 at immutable commit `6af2c95a56ff058cddf0c6febc71512db1d6d19b`. The public annotated tag `refs/tags/v3.1.0` resolves through tag object `1fccece25b28c99bcbbf26881edc336c586f6d5e` to that commit. This relationship was independently verified from the public Git remote before adoption. |
| 8 | + |
| 9 | +The accessibility job selects Node.js 22 explicitly. The action requires Node.js 22.12.0 or later and runs axe-core 4.12.1 through Puppeteer 25.10.0. Local acceptance used Node.js 26.7.0, which satisfies that runtime floor, with the same scanner dependencies from the v3.1.0 source checkout. |
| 10 | + |
| 11 | +All three scans use `fail-on: major` without a baseline. Confirmed critical or serious standards violations block. Moderate, minor, and best-practice-only findings remain advisory. Unknown violation impact, potentially major incomplete evidence, missing coverage, and scan errors cannot pass. |
| 12 | + |
| 13 | +## Built surfaces and route coverage |
| 14 | + |
| 15 | +The tested source was the clean v1.2.0 baseline at `51abb92806393ae4ff0e6e671e77fe383ae0f690` plus the reviewed accessibility changes described below. |
| 16 | + |
| 17 | +| Surface | Build or source identity | Required routes | Result | Result SHA-256 | |
| 18 | +|---|---|---:|---|---| |
| 19 | +| Template default | `node scripts/build.js`, transient `docs/`, `https://example.com/` rewritten to the local origin | 22/22 sitemap routes | Pass | `67e34ff3d895103d4edbbfebe74f795cd1fb711779e075e8d3593ce914d8cfec` | |
| 20 | +| Canonical root landing | Hand-maintained root `index.html`, root fixture sitemap, Pages root unchanged | 1/1 reviewed route | Pass | `e1492560ce7ae26b34d57ef3f3558871b2013d6c65b1eac4e186d0ae55127f30` | |
| 21 | +| Canonical demo | `KAC_OUTPUT_DIR=demo KAC_SITE_URL=https://knowledge-as-code.com/demo/ KAC_REPO_URL=https://github.com/snapsynapse/knowledge-as-code-template node scripts/build.js` | 22/22 sitemap routes | Pass | `d8cbce799fe5ec0b90def3a6b127d6b034b3c61fe2f479ad480a5f61dafef2fc` | |
| 22 | + |
| 23 | +Each final result contains zero confirmed major findings, zero nonblocking findings, zero unknown-impact violations, zero blocking or advisory incomplete candidates, and zero scan errors. The result files are local execution evidence and are identified here by digest; they are not shipped as product artifacts. |
| 24 | + |
| 25 | +The initializer golden path passed after the source changes. It continues to generate the supported fork structure and derives `.github/workflows/pages.yml` without moving the canonical repository's root Pages source. The generator's Node.js 18 and 20 compatibility matrix also remains in place; Node.js 22 is specific to the accessibility job. |
| 26 | + |
| 27 | +## Findings and repairs |
| 28 | + |
| 29 | +The initial template and demo scans had no confirmed violations, but each was inconclusive with 380 serious incomplete candidates across all 22 routes. A body gradient prevented deterministic contrast evaluation for 296 color candidates and 84 links. The root landing had one confirmed serious link distinction violation on the `PUBLISH-MCP.md` link plus 14 serious incomplete candidates involving a roleless labeled wordmark, decorative punctuation, and gradient-backed text. |
| 30 | + |
| 31 | +Repairs were made in the owning sources and regenerated into both output trees: |
| 32 | + |
| 33 | +- The generated site uses the existing dark or light background token as a solid page background so text contrast can be evaluated deterministically. |
| 34 | +- Prose, list, breadcrumb, and footer links are visibly underlined. |
| 35 | +- Timeline rails and markers are real decorative elements, relationship arrows are expressed as the words “maps to,” matrix counts have descriptive accessible names, and empty matrix cells retain “Not covered” text for assistive technology. |
| 36 | +- The root wordmark has an image role, decorative separators and file arrows were removed, the confirmed link is underlined, and promotional statistics retain real text on a solid backing over the decorative gradient. |
| 37 | +- The generated skip link and back-to-top control choose black or white foreground text from each configured accent color. |
| 38 | + |
| 39 | +No axe rule was disabled, no route was skipped, and no baseline was created or refreshed. |
| 40 | + |
| 41 | +## Theme checks |
| 42 | + |
| 43 | +Targeted axe checks covered the root landing under light and dark `prefers-color-scheme` emulation. The generated template and canonical demo index, matrix, and timeline pages were checked after applying and settling the same `light-mode` class changed by their theme button, and again in the default dark state. All 14 page-and-theme cases returned zero violations and zero incomplete candidates. |
| 44 | + |
| 45 | +The root highlighted heading text measured 17.40:1 against the light page background and 16.34:1 against the light highlight; the dark equivalents were 16.62:1 and 13.69:1. The generated back-to-top glyph measured 7.29:1 in light mode and 10.48:1 in dark mode. Its control boundary measured 6.70:1 and 8.51:1 respectively. |
| 46 | + |
| 47 | +This automated result covers only the routes, themes, and rules described here. It does not establish complete WCAG conformance or replace manual testing. |
0 commit comments