Accessibility Statement

We target the Web Content Accessibility Guidelines version 2.2 at level AA across the employee portal, the company workspace and this marketing site.

A payroll and HR system is not optional software for the people who work in it. If someone cannot apply for leave or read their own payslip without help, that is a defect, not a preference.

The following are implemented and tested as part of our normal release process.

• Full keyboard operation of navigation, forms, tables, dialogs and the approval flows.
• Visible focus indicators that survive our theming, rather than being removed for looks.
• Text contrast meeting AA, including on the pink accent used for primary actions.
• Labels, roles and error messages exposed to screen readers, with form errors announced rather than only coloured red.
• Respect for the reduced motion setting: the scroll reveals, count up figures and marquees all resolve to a static state.
• Text that reflows to 320 pixels wide and survives zoom to 200 percent without loss of content.
• Semantic headings and landmarks, so a screen reader user can skip to a section instead of reading the page in sequence.

Publishing an accessibility statement that claims everything works would be worth very little. These are the gaps we know about.

• The payroll comparison and variance tables are wide and dense. They are navigable, but reading them with a screen reader is slower than it should be, and we are reworking the header associations.
• Some charts convey a trend by shape alone. Underlying figures are available in the adjacent table, but the chart itself is not yet independently readable.
• Drag and drop reordering, in the recruitment pipeline and goal weighting, has keyboard equivalents that are less discoverable than the mouse path.
• A few date pickers announce the selected date less clearly than they should on Android screen readers.

Automated checks run in continuous integration and block a release on a new violation. Automated tooling only catches part of the picture, so we also test by hand.

Manual passes use NVDA with Firefox and Chrome on Windows, VoiceOver with Safari on macOS and iOS, TalkBack on Android, and keyboard only operation with no pointing device.

Write to accessibility@kiko.co. Describe what you were trying to do, the assistive technology and browser you were using, and where it broke down.

We acknowledge within 2 business days. Anything that blocks a person from completing a core task, such as viewing a payslip, applying for leave or clocking in, is treated as a Severity 1 issue under the Service Level Agreement regardless of how many people it affects.

If you need information from the platform in an alternative format while a fix is pending, ask and we will provide it.

This statement is reviewed every six months and after any significant redesign. Each review updates the gaps above, including removing the ones we have closed.