Accessibility Statement

1.Commitment

A revenue-cycle specialist works in this software for seven hours a day. If it is unusable with a keyboard or a screen reader, that is not an edge case — it is somebody's job made impossible.

We target WCAG 2.1 Level AA.

2.What is in place

• Semantic landmarks and a logical heading order on every page.
• Every form control has a label; filters and search are labelled for screen readers.
• Visible focus on interactive elements, and keyboard operation throughout — no mouse-only controls.
• Colour contrast meeting AA for body text and interface text.
• Colour is never the only carrier of meaning; status is stated in words as well.
• Data figures use tabular numerals so columns align for anyone scanning them.
• All motion respects prefers-reduced-motion — animations stop entirely rather than running slower.
• Graphics carry text alternatives describing the finding, not just the shape.

3.Known limitations

This statement describes practice and intent; it is not a certification of conformance.

Known limitations:

• The platform has not been tested end to end with JAWS or NVDA.
• Some dense data tables have not been verified for screen-reader navigation at width.
• No high-contrast theme is offered.

4.Tell us

If something here does not work for you, say so and we will fix it — that is a bug, not a feature request, and it is treated as one. Include the page, what you were using, and what happened.

We will acknowledge within three business days and tell you what we intend to do.