Accessibility statement

What we have tested, and what is still not right.

Everyone in your team uses HollyHR, so it has to work for everyone. This page says what we have tested and fixed, what is still imperfect and how to tell us about a problem. We have not had an independent audit, so we do not claim WCAG conformance.

This statement covers HollyHR in the app and on this website. It comes from Holly Software Limited. Last reviewed 21 November 2026.

Where we standFrom our own testing, not an outside audit
  • Independent auditNot yet
  • Last tested18, 19 and 21 November 2026
  • Checked atDesktop, phone width and 200% zoom
What we have tested

Checked by tools and by hand.

We aim for WCAG 2.2 AA, the standard most UK organisations use. These are the checks behind that aim.

Automated checks

Every component in our design library carries an axe-core check that fails on a violation. A browser run checks app pages against the WCAG 2.2 A and AA rules at desktop and phone sizes. We run it on request, not on every release.

80 pages across the app

We went through the pages an employee, a manager, HR and a System Admin can open. Each was checked at desktop width, at a 390 px phone width and at 200% zoom for sideways scrolling, headings, landmarks and small tap targets.

By keyboard and screen-reader structure

We walked the main journeys with the keyboard only: the menu, search, booking time off, reporting sickness, filters, Add person, documents, onboarding, notifications, approving leave and Settings. On 21 November 2026 we also walked pay, bank details and signing a document (send, sign and counter-sign) by keyboard, checking tab order, where focus lands, Escape and the error messages. A screen-reader emulation, the browser's accessibility tree, stood in for the names, roles and announcements a screen reader reads. Each of those three flows now has an automated keyboard test.

What we fixed

Problems the testing found, now fixed.

The testing found a few real problems, mostly on phones and with the keyboard. These are fixed, and each is in the changelog.

Phone menu
Tab reaches every item in the phone menu, and it announces when it closes.
Leave balances
Managers see Remaining leave beside the leave type and can scroll the balance table by keyboard.
Keyboard focus
You can see which person you are on in People. Focus returns to the button after you close a time-off form, and moves into the sickness date forms.
Tap targets and contrast
Buttons and profile links are easier to tap on a phone, and notification counts and the phone menu name meet AA contrast.
Pay, banking and signing
Focus stays where you were when you close a pay, bank details or signing form, or when a save fails. Errors are read out as they appear. Pay history and copy buttons say what they act on, and signing a document moves you to the result.
Pop-ups
Dialog buttons follow the order you see them in, and long forms scroll inside the pop-up with the title and buttons in view.
What is not right yet

What we have not tested, and what is still imperfect.

We would rather you know the limits than find them yourself.
No independent audit
An outside specialist has not audited HollyHR against WCAG 2.2 AA, so we do not say it meets it.
No real screen readers
We have not tested with VoiceOver, NVDA or TalkBack, or on real phones. That includes the 21 November walk of pay, bank details and signing. Our checks used the browser's accessibility tree and axe-core, so they miss what only a person using a screen reader would hit.
Automated checks only
We have not walked the benefits, equipment and training dialogs, billing, imports or company closures by keyboard. They had automated and layout checks only.
Signing a document
Drawing a signature needs a mouse, pen or finger. Typing your name signs the document just as well, and that works by keyboard. The page shows the document as an image of each page, so a screen reader cannot read its text there. The Open the PDF link opens the file itself, and how well that reads depends on the PDF you send. We have not tested either with a screen reader.
Ask Holly
The AI assistant was not part of the sweep.
Zoom and text spacing
We checked 200% zoom as a 720 px wide window, not pinch zoom, and we have not tested custom text spacing.
This website
The marketing site and help centre were not in the sweep. Their components get the same automated check as the app's.
Tell us

Report a problem, or ask for another way to do something.

If something in HollyHR is hard to use, tell us. Say the page, what you were trying to do, your device and browser, and any assistive technology you use. If you cannot use a part of HollyHR, say what you need to get done and we will find another way with you.

The same working day, during UK support hours, is when we aim to send a first reply from a person. This is an aim, not a guarantee. It counts the first reply from a person, not an automatic acknowledgement, and it is not a deadline to fix the problem.

1. Email supportWrite to support@hollyhr.com. A person reads it.
2. We fix it or say why we cannotWe fix what we can, tell you what we changed and add it to this page if it is something others may hit.
3. Not happy with the reply?Email info@hollyhr.com and a founder will look at it. You can also contact the Equality Advisory and Support Service, which gives free advice on discrimination.
Technical information

How this statement was prepared.

Standard we aim for
WCAG 2.2 level AA. Compliance status: not independently audited.
What this covers
The HollyHR app and this website, www.hollyhr.com.
How it was prepared
From our own testing on 18, 19 and 21 November 2026, and our automated checks. We update it when we fix or find something. Last reviewed 21 November 2026.