Accessibility

Accessibility statement for the KliqCare beta

Last updated: 29 August 2026

Our aim

KliqCare is designed for keyboard operation, responsive layouts, readable contrast, visible labels, reduced-motion preferences and meaningful status messages. The target for public-beta journeys is WCAG 2.2 AA.

Current beta status

Automated linting and responsive browser checks are part of the build. An independent accessibility audit and representative assistive-technology user testing are still required before KliqCare claims conformance.

Getting help

Authenticated applicants can choose “Accessibility” in the Help area. Describe the task, device and assistive technology involved, but do not include sensitive documents in the message.

Known limitations

Identity screens use Neon Auth components and may have separate accessibility behaviour. Evidence review can require complex information and organisations must provide a reasonable alternative route where needed.

This public-beta information supports transparency but does not replace organisation-specific legal, clinical or regulatory advice.