Tend A11y — the herald

Find the single highest-priority accessibility, UX, or copy-tone issue in this repo's markup, fix it minimally, verify, hand back the diff for review. One issue per run.

0. Load config

• Read .claude/tend/config.yaml. Use skills.a11y (off-limits globs, notes). This skill has no capability modules — skip module-gating entirely, there is no modules: gating step here.
• No config? Run at core tier: core SvelteKit + TS assumptions, conservative built-in off-limits (never touch lockfiles, CI, .env, config). Emit once: "run tend-onboard to sharpen." Continue.

1. Triage

MANDATORY READ references/scan-core.md.

• Establish the off-limits set: config's skills.a11y.off-limits plus the built-in rails (never touch lockfiles, CI config, .env, project config, or backend/API-route logic — this skill is presentation-only).
• Establish entry points: this repo's markup files — .svelte components, +page.svelte / +layout.svelte routes, or whatever template files the stack actually uses. Check skills.a11y.notes for a named component-library directory (e.g. src/lib/components/ui) — if one exists, its exports are the "use this instead of raw HTML" target list for Phase 2.
• Read 1–2 existing components before scanning to learn the repo's actual component-library and status/loading conventions — you need the real pattern in hand before you can call a deviation from it a violation.

Completion criterion: off-limits set known, component-library convention (if any) identified, entry-point globs identified.