Find and understand
Navigation, breadcrumbs, headings, page titles, and link language should help readers predict where they are going and scan without reading every line.
Access for more minds
Accessibility
The interface is designed for keyboard use, readable contrast, reduced motion, clear focus states, and responsive text.
At a glance
The practical scope of this page.
| Keyboard | Core navigation, menus, accordions, check-ins, and care-planning controls are intended to work without a mouse. |
|---|---|
| Screen readers | Landmarks, labels, heading order, current-page states, live regions, and alternative text provide structure. |
| Visual access | Readable contrast, visible focus, responsive text, and layouts that do not rely on color alone. |
| Motion | Reduced-motion preferences disable non-essential transitions and smooth scrolling. |
| Cognitive access | Plain language, short task sequences, consistent navigation, and explicit safety boundaries. |
Interaction
Navigation, quizzes, accordions, and controls are operable with a keyboard and expose useful labels.
Motion and color
Reduced-motion preferences are respected and meaning is not carried by color alone.
Feedback
If an access barrier remains, use the contact page to describe the page, device, browser, and assistive technology involved.
Accessibility across the whole task
A control can be technically labeled while the overall journey remains difficult. Testing should follow what a person is trying to accomplish.
Operate and recover
Menus, forms, accordions, reset controls, validation, and focus movement should work from a keyboard and make it clear how to undo or leave an interaction.
Read and reflow
Text should remain usable with zoom, larger fonts, narrow screens, high contrast needs, and reduced motion. Tables may scroll without forcing the entire page sideways.
Complete the real task
Testing should include opening support information, completing and clearing a check-in, printing a worksheet, finding a source, and reporting a barrier—not only loading the homepage.
Test access through a real task
Try keyboard and zoom behavior while browsing the advice library or completing a private reflection, not only on this policy page.
Every self-check page uses labeled controls, visible focus, a progress indicator, and a way to clear the in-browser result.
If a barrier remains, use the contact page to report the address, task, browser, device, zoom, and assistive technology involved.
Report an access barrier effectively
A detailed report helps reproduce the problem without requiring you to diagnose the technical cause.
- Include the page address and the task you were trying to complete.
- Name the device, browser, zoom level, and assistive technology when known.
- Describe what happened, what you expected, and whether a workaround exists.
- Avoid sending private health answers or medical records with the report.
- Say if the problem blocks urgent support information so it can be prioritized.
Common questions
What accessibility standard do you use?+
The interface aims to follow WCAG principles of perceivable, operable, understandable, and robust content, while recognizing that conformance requires continuing testing.
Can I enlarge the text?+
The responsive layout is intended to reflow with browser zoom and larger text settings.
Why might an external site behave differently?+
External services control their own design and accessibility. Report barriers to that provider as well as to Yourself when the link itself creates a problem.
Can I request another format?+
Use the contact page to describe the content and format you need. Availability may depend on the material and operator capacity.