Resource
Accessibility
PWA UI supplies accessible structure and interaction defaults, but accessibility remains a property of the finished application—not a component-library certification.
Built into the components
- Base UI provides focus trapping, Escape dismissal, focus restoration, and dialog semantics for overlays.
- Navigation components expose landmarks, active-page state, visible labels, and accessible badge text.
- Touch-first actions use at least 44 × 44 CSS-pixel targets.
- Motion is suppressed when the user requests reduced motion.
- The documentation viewport preserves browser zoom.
Your responsibilities
- Give every sheet and dialog a meaningful title, with a description when it adds context.
- Use specific names for icon-only controls and informative badges.
- Verify focus order, contrast, zoom, text reflow, and error handling after applying your theme and content.
- Test with keyboard-only navigation and the screen readers used by your audience.
- Do not disable important actions solely because the browser reports an offline state.
Validation policy
Automated semantic checks run in the browser suite. Manual keyboard, VoiceOver, TalkBack, zoom, contrast, and reduced-motion checks remain release requirements because automated scans cannot establish conformance on their own.