Does Claude Code write accessible components by default?

Yes, we encode WCAG 2.2 AA as a hard rule in CLAUDE.md: every interactive element gets a proper role, accessible name, keyboard handler, visible focus ring, and aria-state attributes (aria-expanded, aria-pressed, aria-current, aria-invalid, etc.). We pair Claude Code with axe-core in CI, no PR merges with a11y violations. Color-contrast is checked against tokens at design-token compile time, so a 4.4:1 pair fails the build before code is even written. Manual NVDA + VoiceOver pass before sign-off on any complex widget (dialogs, comboboxes, date pickers).