Aspire.dev works to the WCAG 2 Level AA accessibility standards. I asked Claude to check the site's compliance. It identified the following issues:
No blocking WCAG AA failures, but a real, fixable set of issues that cluster into a small number of root causes:
- Content (594 files): the biggest single item is a heading-level skip (## → ####, missing ###) repeated across ~50 integration "connect" pages — one authoring pattern, not 50 separate bugs. Plus a handful of one-off issues: a duplicate ARIA-faked <h1>, one vague "this link" link text, one filename-style alt text, and YouTube embeds relying only on auto-captions.
- Automated scan (28 representative routes via axe-core, wcag2a+wcag2aa): two sitewide template issues — scrollable code blocks that aren't keyboard-focusable, and the skip-link sitting outside a landmark — plus contrast failures on a few specific chip/pill styles, a list-markup issue on one page, and duplicate unlabeled landmarks on 15 pages. Your existing wcag-aa.spec.ts only covers 4 routes, so it wasn't catching most of this.
- Components (108 files): mostly solid — the modal, custom select, tabs, carousel, and looping media all handle focus/keyboard/ARIA/reduced-motion correctly. Two real gaps: no visible focus state on the release-timeline slider and on individual theme-toggle options."
Aspire.dev works to the WCAG 2 Level AA accessibility standards. I asked Claude to check the site's compliance. It identified the following issues:
No blocking WCAG AA failures, but a real, fixable set of issues that cluster into a small number of root causes: