Keyboard and focus
Interactive controls are designed to work without a mouse, with visible focus, logical order, usable touch targets, and non-drag alternatives.
SmoozenExplore
Smoozen accessibility
Wellness planning should be usable by more people.
The current Preview is being built toward WCAG 2.2 AA with semantic headings, labels, keyboard-friendly controls, readable status messages, and explicit no-match and error states.
Our commitments
Clarity is an accessibility feature.
Every surface should explain what is happening, what a person can do next, and when a human decision is required.
Clear status
Loading, error, stale-data, no-match, approval, advisory, controlled-pilot, and denied states are presented as readable messages.
Charts and tables
Visual summaries require an equivalent text or table representation. Color is not the only way to communicate status or comparison.
Motion and contrast
Reduced-motion, increased-contrast, and forced-colors preferences are respected. Responsive previews do not replace real-device testing.
Progressive disclosure
Pricing and portal detail panels use native keyboard-accessible disclosure controls to reduce information overload while keeping the full context available.
Admin safety
Platform and emergency controls remain visibly separate, session-bound, and policy-limited. Emergency access cannot bypass consent, safety, RLS, audit, or client ownership.
Human review
Recommendations remain advisory and can be reviewed, edited, approved, or rejected by authorised people.
Evidence status
A commitment is not the same as a conformance claim.
We separate what is designed into the product from what still needs controlled verification.
Built into the interface
Semantic headings, skip navigation, visible focus, readable labels, responsive layouts, and explicit denial and empty states are part of the current Preview foundation.
Needs controlled verification
Keyboard-only, screen-reader, forced-colors, reduced-motion, and real-device checks require an approved Preview window and named evidence owner.
Before public launch
Formal conformance review, issue triage, remediation evidence, and owner approval remain required. Passing automated checks alone is not a launch decision.
Validation matrix
Know what is built and what still needs observation.
These labels keep implementation evidence separate from a formal conformance claim.
| Area | Current foundation | Next evidence |
|---|---|---|
| Keyboard and focus | Foundation present | Manual Preview evidence pending |
| Status announcements | Semantic status and landmarks present | Manual Preview evidence pending |
| Forced colors | Fallback borders and focus styles present | Manual Preview evidence pending |
| Reduced motion | Preference suppression present | Manual Preview evidence pending |