Environment: Windows 11, bash shell. Project root: J:\CLAUDE\PROJECTS\Wakeword (master).

PROBLEM
Run an accessibility audit on https://violawake.com/ (landing, register, login, pricing, privacy, terms — public pages) and produce a remediation report. We've shipped polish but never confirmed WCAG-AA compliance. Investors, accessibility lawsuits, and screen-reader users all care about this.

INVESTIGATE FIRST
1. Check tooling: `node --version`, `npx --version`. Lighthouse / axe / pa11y are the typical tools.
2. Pick ONE tool that's reliable on the live site (lighthouse-cli is cleanest if available; pa11y works too).
3. Try `npx --yes @lhci/cli@latest collect --url=https://violawake.com/` OR `npx --yes pa11y https://violawake.com/`. Use whichever installs and runs cleanest.

WHAT TO TEST
For each public page (/, /pricing, /register, /login, /privacy, /terms):
- Color contrast (WCAG AA = 4.5:1 for normal text)
- Form label associations (do all input fields have <label for=...>?)
- Heading order (h1 → h2 → h3, no skips)
- Image alt text
- Focus order on Tab navigation
- ARIA usage correctness
- Page language (`<html lang="en">`)
- Link/button distinguishability
- Semantic HTML (button vs <div onClick>)

DECIDE & IMPLEMENT
Produce a report at `tests/live/ACCESSIBILITY_AUDIT_2026-05-07.md` with:
- Executive summary: pass/fail at WCAG AA
- Per-page issue list, ordered by severity
- Suggested fixes (file + line + concrete code change), but DO NOT implement code fixes yet — this is an audit, not a remediation pass

If the audit reveals trivial fixes (e.g., missing `lang="en"` attribute, missing `<label htmlFor>`), implement them in a separate small commit. But do not undertake big restructuring.

CONSTRAINTS
- Read-only on the website (just probe).
- Stage explicit files. Logical commits.
- Don't push.

PROVE IT
1. Show the auditor's raw output (head -100).
2. Confirm `tests/live/ACCESSIBILITY_AUDIT_2026-05-07.md` exists and has at least the executive summary section.
3. If you implemented fixes, run `cd console/frontend && npm run build` to confirm it still builds.

REPORT
- Tool used + version.
- Score / failure count summary.
- Top 5 issues by severity.
- Files modified (audit doc + any fixes).
- Commit SHA(s).
