techtank-site: Skill for Claude Code

Accessibility

The floor, not a cleanup pass. Appearance is the design contract's concern, where content lives is the data skill's, and component shape is the components skill's.

The baseline

1. WCAG 2.0 AA is the legal floor, 2.2 AA is the target. AODA and the ACA both require AA. Cite the success criterion in every defect report and fix: the criterion decides whether a fix is sufficient.
2. Automated checkers find the minority of it. WAVE, axe, and the IBM Equal Access checker catch missing names, contrast, and malformed ARIA. They miss focus order, a ring lost against its background, a card nobody can tab to, and motion that never stops. No route counts as audited without a keyboard-only pass and a screen reader pass.
3. A third-party embed caps conformance at its own. An iframe's internals are not reachable or restyleable from the host page. Name the ceiling, keep the parts you own correct (an accurate title, a reachable fallback), and record the defect against the vendor. Never report a vendor's defect as fixed, and never fake a fix around it.

Document structure

1. One main per page. The persistent shell owns it and routes render sections inside it; a nested layout never renders its own.
2. Landmarks are semantic elements, not divs with roles: header, nav, main, footer, section, article. Each landmark of a kind is named at the call site, never inside the component, because the name describes what that instance navigates: a site nav and a section sub-nav otherwise both announce as "navigation".
3. Heading levels never skip. An h2 followed by an h4 is a defect on its own.
4. A list of title-and-description pairs is a description list. dl with dt and dd models it exactly. Reach for it before inventing a heading level for a stepper, a glossary, or a spec table.
5. Disclosures use details and summary. The native element brings keyboard behaviour, state, and in-page find; a scripted accordion usually drops in-page find.