QAPIHubTry the Demo →

Accessibility Statement

Last updated: March 2026.

Our Commitment

QAPIHub is committed to ensuring digital accessibility for people of all abilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to ensure we provide equal access to all users.

As a healthcare compliance platform used by nursing facilities and assisted living residences, we recognize that accessible design is essential — not optional. Our users include administrators, directors of nursing, medical directors, and quality consultants who rely on QAPIHub daily for regulatory compliance work.

Conformance Standard

QAPIHub targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities.

Our accessibility efforts include:

  • Color contrast: All text meets WCAG 2.1 AA minimum contrast ratios (4.5:1 for normal text, 3:1 for large text)
  • Keyboard navigation: All interactive elements are operable via keyboard with visible focus indicators
  • Touch targets: Interactive elements meet minimum 44×44 pixel touch target size (WCAG 2.5.5)
  • Form labels: All form inputs have programmatically associated labels for screen reader compatibility
  • ARIA attributes: Semantic markup and ARIA roles, states, and properties are used to convey meaning and state to assistive technologies
  • Responsive design: The interface adapts to different screen sizes and supports text resizing up to 200%

Known Limitations

While we strive for full accessibility, certain limitations may exist:

  • AI-generated content: Documents generated by the AI assistant produce markdown-formatted text. While this content is rendered with appropriate heading structure and list formatting, complex generated tables or data visualizations may have limited screen reader support.
  • Third-party data: Data from CMS Care Compare and CDPHE public APIs is displayed as received. Formatting of this external data may not always meet our accessibility standards.
  • PDF exports: Generated PDF documents may require additional accessibility remediation for full screen reader compatibility.

We are actively working to address these limitations and improve accessibility across all areas of the platform.

Compatibility

QAPIHub is designed to be compatible with the following assistive technologies:

  • Screen readers (NVDA, JAWS, VoiceOver, TalkBack)
  • Screen magnification software
  • Speech recognition software
  • Keyboard-only navigation

QAPIHub is built with modern web standards (HTML5, ARIA) and is best experienced in current versions of Chrome, Firefox, Safari, and Edge.

Feedback & Contact

We welcome your feedback on the accessibility of QAPIHub. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

QAPIHub Accessibility Support
Email: shinu.mammen@qapihub.com

We aim to respond to accessibility feedback within 2 business days and to resolve reported issues as quickly as possible.

Assessment & Review

QAPIHub assesses accessibility through a combination of:

  • Automated testing against WCAG 2.1 AA criteria
  • Manual keyboard and screen reader testing
  • Color contrast verification across all UI components
  • Touch target size auditing for mobile users

Our most recent accessibility review was completed in March 2026.

WCAG 2.1 Level AA · Last reviewed March 2026