a11y-check

# Accessibility Audit Evaluate user-facing work against the criteria that BIND TO ITS SURFACES. Accessibility is a design constraint, not a polish step (Downe Principle 11) — and an instrument aimed at a surface the product does not have measures nothing while looking like a failure. ## STEP 1 — SURFACE GATE. Run this BEFORE the checklist, every time. **The checklist below is written for web pages. Most products are not web pages.** Detect which user-facing surfaces this product actually has, from the repository, and evaluate ONLY the criteria that bind to them. Profiles and detection hints: `engine/canvas-guidance.yml#surfaces` — `web` · `rendered_markdown` · `terminal` · `native_app` · `video_audio` · `document` · `headless`. A product commonly has several. State which you found and how, in the output. **THE RULE THAT DECIDES EVERY RATING:** | situation | rating | |---|---| | the surface is ABSENT | **`n/a`** — and say which surface is missing | | the surface is PRESENT and you measured it | `pass` / `partial` / `fail` on the evidence | | the surface is PRESENT and you did NOT measure it | `not-assessed` — a real gap, it could have been measured | **MARKING A CRITERION `fail` BECAUSE ITS SURFACE DOES NOT EXIST IS A CATEGORY ERROR.** It manufactures a defect out of a product's shape, and a done-bar built on it fails for a reason no work can fix. **MEASURED, WHICH IS WHY THIS SECTION EXISTS.** On 2026-09-03 this skill's checklist was applied to Mycelium — a terminal pr...