Make the experience available.
Names, focus, feedback and preferences are part of the design. Verify them in the context where people will actually use them.
Implementation previewAutomated checks and targeted browser verification provide bounded evidence. No blanket WCAG certification or complete screen-reader/platform coverage is claimed.
Review the person’s whole interaction
Use these checks on the actual screen, with its content and state. A token or component name cannot establish the result.
Accessible names, labels, roles, values and live status messages.
Keyboard focus order, visible focus, dismissal and restoration.
Contrast for the actual foreground/background/state pair in each theme.
Reflow, browser zoom, long/localized content, touch targets and text scaling.
Reduced motion and preference changes during an interaction.
Make the behavior tangible
These live references give you a place to inspect the choices before reviewing a product integration.
Names and feedback
Follow a label through editing, invalid input and correction.
Explore the reference ColorTheme and contrast
Inspect the actual semantic pair on the surface where it is used.
Explore the reference MotionMotion and preferences
Compare motion with explicit playback and reduced-motion preferences.
Explore the referenceOpen Search, move between its controls, dismiss it with Escape, and check where focus returns. In a component gallery, reach a named story, filter the list, and recover from a query with no matches.
Open the interaction review taskKeep unverified coverage visible
Carry these limitations into a platform review or accessibility handoff.
- Full-library manual VoiceOver and TalkBack coverage is not established.
- Vue, Swift and Kotlin consumers need their own compiled and accessibility verification.
- The imported web typography scale clamps its host-driven font-scale variable; native accessibility text sizes require separate adaptation and review.