Back to home

Accessibility Statement

Last updated: July 16, 2026

Our Commitment

HolliHQ is committed to making Holli usable by as many people as possible, including people with disabilities. Accessibility is part of how we build the product, and we keep improving it as the platform develops.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible for people with disabilities and more usable for everyone.

Conformance Status

Holli is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not yet fully conform to the standard. Holli is in active development, and we work on accessibility improvements as part of our regular development process.

This is a self-assessment by our development team. We have not yet commissioned an independent accessibility audit.

What We Do

Accessible Components

Holli's interface is built on component libraries (Radix UI primitives) that provide strong accessibility defaults, including keyboard interaction patterns, focus management, and ARIA attributes for dialogs, menus, dropdowns, and form controls.

Keyboard Navigation

  • Interactive elements are reachable and operable by keyboard
  • Visible focus indicators on interactive elements
  • Drag-and-drop reordering (for example, in the intake form builder) also works with the keyboard via accessible drag handles

Structure and Screen Readers

  • Semantic HTML with heading structure on pages
  • ARIA labels on icon-only controls
  • Form fields with associated labels and descriptive error messages
  • Live regions for some dynamic updates, such as toast notifications

Visual Design

  • We aim for WCAG AA colour contrast in the interface
  • Text can be resized with browser zoom without loss of core functionality
  • Consistent navigation and layout across the application
  • Loading states and progress indicators for longer operations

Known Limitations

Some parts of Holli do not yet meet our accessibility target. Known limitations include:

  • Skip navigation: the application does not yet provide skip links to bypass repeated navigation.
  • AI-generated content: AI-generated summaries and documents may occasionally contain formatting that is awkward for screen readers. Practitioners review these outputs before use.
  • Uploaded documents: PDFs and other documents uploaded by practitioners keep their original accessibility characteristics. We recommend uploading text-searchable, well-structured documents where possible.
  • Live transcription: real-time transcription depends on audio quality and may lag or contain errors, so it should not be relied on as the sole accessible record of a session.
  • Complex screens: some data-heavy screens, such as calendar views, may be harder to navigate with assistive technology. We are working on improvements.

Assistive Technology Compatibility

Holli is a standard web application built with HTML, CSS, JavaScript, and WAI-ARIA, and is designed to work in current versions of major browsers (Chrome, Firefox, Safari, Edge) with common assistive technologies such as screen readers (VoiceOver, NVDA, JAWS) and screen magnification. If you find a combination that does not work well, please tell us.

Third-Party Content

Some content in Holli comes from third parties or from other users, such as documents uploaded by practitioners and AI-generated text. We cannot always guarantee the accessibility of this content. We encourage practitioners to upload accessible documents and to review AI-generated content for clarity before sharing it with clients.

Feedback & Assistance

We welcome your feedback on the accessibility of Holli. If you encounter an accessibility barrier, please let us know:

Email: hello@hollihq.com

Response time: we aim to respond within 2 business days

When reporting an issue, it helps if you include:

  • The page or feature where you encountered the issue
  • A description of the problem
  • The assistive technology you were using (if applicable)
  • Your browser and operating system

Formal Complaints

If you are not satisfied with our response to an accessibility concern, you may raise a complaint with:

  • Australia: Australian Human Rights Commission athumanrights.gov.au
  • Elsewhere: the relevant equality or human rights body in your jurisdiction

Continuous Improvement

Accessibility is ongoing work, not a one-off checklist. We address accessibility issues as part of our regular development cycle, prioritise barriers reported by users, and review new features against WCAG 2.1 AA as we build them. This statement was last reviewed on July 16, 2026.

Related Policies