Accessibility Statement

Native Keeper — operated by NeonStack Ltd (company number 16933096) — is committed to making our product usable by everyone, including people with disabilities and people who rely on assistive technologies.

This Statement covers:

• Our website at nativekeeper.com (marketing pages, dashboard, documentation)
• The Native Keeper application used by administrators to manage workforce records
• Any employee-facing experiences we release as our roadmap ships (mobile app, self-service portals, engagement features)

We treat accessibility as an ongoing programme, not a one-time milestone. This matters especially for us because our customers use Native Keeper to manage their workforce — and some of those workers may themselves have disabilities.

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA published by the W3C. This is the global benchmark referenced by:

• The UK Equality Act 2010 (via accessibility guidance from the GDS and EHRC)
• The European Accessibility Act (Directive (EU) 2019/882), applicable since 28 June 2025
• The US Americans with Disabilities Act (ADA) Title III (via DOJ guidance)
• Section 508 of the US Rehabilitation Act
• Similar frameworks in Canada, Australia, and other jurisdictions

Where reasonable, we also align with WCAG 2.2 criteria, which add improvements for cognitive accessibility and mobile use.

Conformance status: Partially conformant with WCAG 2.1 Level AA.

"Partially conformant" means that most of the Service meets the standard, but some parts do not yet fully conform. We document known issues in Section 5 and address them on an ongoing basis.

The most recent self-assessment was conducted on [DATE OF YOUR LAST INTERNAL AUDIT] by the Native Keeper team. We have not yet engaged a third-party accessibility auditor; we plan to do so as the product matures.

If you're a public-sector buyer or enterprise procurement team and need a VPAT (Voluntary Product Accessibility Template) or formal conformance report, contact legal@nativekeeper.com and we will provide what we can, including being honest about gaps.

• Keyboard navigation: All primary user flows can be operated with a keyboard, with visible focus indicators
• Screen reader support: Semantic HTML, ARIA landmarks, and meaningful labels on interactive elements
• Colour contrast: Text meets WCAG AA contrast ratios in our default themes
• Resizable text: Text can be resized up to 200% without loss of functionality
• Skip links: Provided on key pages to skip past repetitive navigation
• Form labels and error messages: All form inputs have programmatically associated labels and clear, accessible error messages
• Alternative text: Meaningful alternative text on informative images; decorative images marked appropriately
• Reduced motion: We honour prefers-reduced-motion user settings to minimise animation
• Language: Page language declared in HTML

The dashboard where you manage employee records has been designed with accessibility in mind:

• Structured tables with proper headers, so screen readers can announce records logically
• Descriptive action labels — buttons like "Delete record for John Smith" rather than just "Delete"
• Keyboard-navigable search and filter controls
• Accessible date pickers for compliance-expiry management
• Clear focus management when opening modals, drawers, and confirmation dialogs
• Announced status changes — when a record is saved, deleted, or expires, assistive technologies are notified

• Accessible email templates with proper structure, semantic headings, and plain-text alternatives
• Downloadable reports in formats compatible with screen readers (PDF exports include proper tagging where technically feasible; CSV exports work with any assistive technology)

We believe transparency about gaps is more useful than overclaiming. The following are known limitations we are actively working on:

We update this list as we close gaps and as we discover new ones.

We test the Service with the following combinations:

The Service should also work with most other assistive technologies on modern browsers. If you encounter issues with a specific configuration, please tell us — see Section 9.

If you use Native Keeper to manage a workforce that includes people with disabilities, there are things you can do to make the platform work well for everyone:

Our Admin User interface has accessibility features built in. As we ship worker-facing features (mobile app, self-service, engagement), accessibility will be evaluated for each.

If you are a public-sector buyer or enterprise procurement team:

• VPAT (Voluntary Product Accessibility Template): Available on request from legal@nativekeeper.com. Note that our VPAT honestly reflects the partial-conformance status described above; it is not aspirational.
• EAA conformance documentation: Available on request.
• EN 301 549 mapping: Available on request.
• Accessibility roadmap: Available on request for procurement-stage discussions under NDA.

We can usually turn around procurement requests within 5 business days.

If you encounter an accessibility barrier on nativekeeper.com or in the Native Keeper application, please tell us. We treat accessibility reports as a priority.

• Email: legal@nativekeeper.com
• Subject line: Please include "Accessibility issue" so we route it correctly
• What to include: A description of the issue, the URL or page where it occurred, the assistive technology you were using (if any), and the device/browser combination

Our response commitments:

If you reported an issue and aren't satisfied with our response, you have the right to escalate it. In the UK, you can contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com(opens in new tab). In the EU, you can contact the national enforcement body for the European Accessibility Act in your country. In the US, you can contact the Department of Justice or file a complaint under Section 508 where applicable.

We don't believe in publishing roadmaps that we won't keep, but we will tell you that our current priorities are:

• Closing the keyboard-accessibility gap in drag-and-drop interfaces
• Improving screen reader support in dashboards and data visualisations
• Third-party accessibility audit (planned within the next 12 months)
• Publishing a complete VPAT once the third-party audit is done
• Building accessibility as a core design constraint for all roadmap features, especially employee-facing ones (mobile app, self-service, engagement)

We update this Statement when we make material progress on these items.

We review this Statement at least quarterly and update it when:

• We make significant accessibility improvements
• We discover or close known gaps
• Standards (WCAG, EAA, ADA guidance) change in ways that affect our commitments
• A third-party audit is completed
• New features ship that need to be assessed

The "Last updated" date at the top reflects the most recent change.

• Accessibility queries and reports: legal@nativekeeper.com
• General enquiries and support: hello@nativekeeper.com
• Postal address: NeonStack Ltd, The North Colchester Business Centre, 340 The Crescent, Colchester, England, CO4 9AD