Accessibility statement
Roost wants every family member, caregiver and coordinator to be able to use this site and the app, whatever assistive technology they use. This page says how far that is true today, in the structure the W3C recommends for such statements.
Last updated 2 September 2026.
Our commitment
Roost Holdings Inc. is committed to making this website and the Roost app accessible to people with disabilities. The standard we build to is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Our agencies are funded in part by Medicaid, which makes them recipients of federal financial assistance from the Department of Health and Human Services, and the Section 504 rule below applies to them. Accessibility is therefore a compliance target for this product, not a preference.
Conformance status
Partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not yet fully conform to the standard. The parts we know about are listed under known limitations. No independent audit has been carried out yet; the assessment is our own, by the methods described below.
What the product does today
What the site and the app do now:
- Every element that answers a click can be reached and operated from the keyboard. A test walks every screen for a control that answers a mouse and nothing else.
- A visible focus indicator on every control; focus styles are never suppressed.
- A “skip to content” link is the first thing on every page.
- Reduced motion is honoured both from the operating-system setting and from an in-app preference, and the two cannot disagree.
- Form fields are labelled, and hints and messages are linked to the field they describe.
- Sortable tables announce their sort order; disclosures and menus announce whether they are open.
- Icon controls grow to at least 44 by 44 pixels on touch screens.
- The family screens and the caregiver's daily screens are available in Spanish as well as English; the rest of the caregiver screens are being translated.
- Messages to people name who, what and when in the reader's own calendar, never a machine timestamp.
Three of these are held by tests in the product's own suite that fail when they regress: keyboard reachability of every clickable element, reduced motion, and the ban on machine timestamps in messages. The others are reviewed by hand as screens are written.
Known limitations
Despite our efforts, the following are known not to conform yet:
- No automated accessibility scan runs in our integration pipeline yet. The unit tests above run on every change; a page-level scanner (axe) across every route is planned and not built. Until it is, a regression a scanner would catch can reach a release.
- Screen-reader testing has not been done end to end. The product has not been walked with NVDA, JAWS or VoiceOver by a person for every persona, and a manual keyboard pass has not been recorded per persona. Where the markup is right, this will be fine; where it is not, we do not know yet.
- Charts in the analytics consoles carry a table alternative where one has been written and not everywhere. The charting layer is being rebuilt, and text alternatives are part of that work.
- Colour contrast on the design tokens has been checked by hand, not by an automated pass over every token pairing in both themes.
If any of these stops you from doing something, write to us and we will provide the information or the service another way.
How this is assessed
Self-evaluation. The product's own test suite holds the measures above on every change, and the people who build it review new screens against WCAG 2.2 AA as they are written. An external evaluation has not been commissioned; when it is, this section will name the evaluator and the date.
Conformance report on request
An Accessibility Conformance Report (ACR), using the VPAT 2.5 template for WCAG, is produced on request for a payer, a state agency or a health plan that asks for one. Write to support@roost.us with the product surface you need it for.
The Section 504 calendar
The Department of Health and Human Services' rule on web and mobile accessibility under Section 504 of the Rehabilitation Act sets WCAG 2.1 level AA as the standard for recipients of HHS funds, with compliance dates by size of recipient, as extended by HHS:
| Who | By |
|---|---|
| Recipients of HHS funds with fifteen or more employees | May 2027 |
| Recipients of HHS funds with fewer than fifteen employees | May 2028 |
Roost builds to WCAG 2.2 AA, which contains 2.1 AA, and treats the earlier date as the one that applies. Source: HHS, extension of the web and mobile accessibility deadline.
Compatibility and technology
The site and the app are built with HTML, CSS, WAI-ARIA and JavaScript, and are designed to work with the current and previous major versions of Chrome, Firefox, Safari and Edge, on desktop and on phones. The caregiver app can be installed to a phone's home screen and keeps working through a loss of signal. Screen-reader compatibility has not been verified by testing; see the limitations above.
Feedback
We welcome feedback on the accessibility of this site and the app. If you meet a barrier, write to support@roost.us and tell us the page, what you were trying to do, and the browser and assistive technology you were using. A person reads every message. Other ways to reach us are on the contact page.