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.
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.
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.
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.
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.
The testing found a few real problems, mostly on phones and with the keyboard. These are fixed, and each is in the changelog.
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.