Accessibility

ArkCloud Health works towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard referenced by Section 508 and by most healthcare procurement reviews.

These are design-system decisions rather than per-page fixes, which is what makes them hold as new screens are built:

• Colour contrast above the AA minimum. Body text sits at 9.2:1 against the page background and the dimmest text used for content at 6.5:1, against a 4.5:1 requirement. The lowest step in the palette is reserved for disabled states and is never used for content.
• A single visible focus ring. Keyboard focus is drawn once for the whole platform, as a two-tone ring so it stays legible against every surface rather than disappearing on panels close to it in luminance.
• Reduced motion is honoured globally. A single rule at the base layer suppresses animation and transitions when your operating system asks for it, so an individual component cannot opt out by forgetting.
• Zoom is never capped. The viewport does not restrict scaling, and pages are laid out to remain usable down to a 320px viewport.
• Larger targets on touch devices. Dense link lists expand their hit area on coarse pointers rather than relying on the same target as a mouse.
• Landmarks and heading order. Public pages expose navigation, main and footer landmarks with a single h1 and a heading structure that descends without skipping levels.
• Colour is not the only signal. Status is carried by a label as well as a colour, so a red-green distinction is never the sole means of conveying it.

The platform is built with standard HTML semantics and ARIA where semantics are not sufficient, and is intended to work with current versions of screen readers and browser zoom. We test with keyboard navigation and browser zoom as part of ordinary development. We do not currently run a formal test matrix across named screen reader and browser combinations, and we would rather say so than imply coverage we have not measured.

These are open, and listed so that you can judge the impact on your own use before you encounter it:

• No skip-to-content link. Public pages expose a main landmark, but there is no visible skip link at the top of the page, so a keyboard user must tab through the navigation on every page.
• Dense data tables. Some tables in the application scroll horizontally and rely on column order for meaning; their row and column relationships are not yet fully described to assistive technology.
• Charts. Analytics visualisations convey information graphically without a guaranteed text or tabular equivalent alongside every chart.
• Third-party content. Documents and content supplied by customers or third parties - uploaded PDFs among them - are outside our control and may not meet the standard.
• No independent audit. The assessment behind this page is our own review against WCAG 2.1 AA, not an external evaluation.

If something on this site or in the application blocks you, tell us and we will treat it as a defect rather than as feedback. Write to [email protected] with the page or screen, what you were trying to do, and the assistive technology and browser you were using if you know them.

We aim to acknowledge accessibility reports within five business days and to tell you what we intend to do about the issue and when. If you need information from a page that is not accessible to you, ask and we will provide it in another format.

If our response does not resolve the problem, you can escalate to [email protected]. Customers with a signed agreement should also raise the issue through their usual account contact so it is tracked against that agreement.