Accessibility Statement

Our software is used by dispatchers on long shifts, mechanics in a loud shop, drivers in a cab, and parents on an old phone in bright sunlight. Accessibility is not a compliance exercise for us — it is the difference between a tool that works at 5:45am and one that does not.

Our target

We aim to meet WCAG 2.2 Level AA across this website and the Nice fleet platform, including the driver and parent applications.

What we do today

• Semantic HTML with a logical heading order and landmark regions.
• A visible "skip to content" link, and a keyboard-operable path through every interactive element.
• Visible focus indicators that are not removed for aesthetic reasons.
• Text and interface colours checked against AA contrast ratios on both our light and dark surfaces.
• Touch targets of at least 44 by 44 pixels.
• Text that reflows without horizontal scrolling down to 320 pixels wide, and remains usable at 200% zoom.
• Meaningful alternative text on images, and decorative graphics hidden from assistive technology.
• Form fields with real labels, clear error messages, and status updates announced to screen readers.
• Respect for the operating system "reduce motion" preference.

Known limitations

We are a young company and this statement reflects our current honest position rather than a completed audit.

• We have not yet commissioned an independent third-party accessibility audit.
• Live map views convey some information spatially. We are working to ensure every fact shown on a map is also available as text.
• Some PDF exports may not yet be fully tagged for screen readers.

Tell us when we get it wrong

If any part of this site or our software is difficult or impossible for you to use, please tell us. Include the page or screen, what you were trying to do, and the assistive technology you use if that is relevant.

Email info@nicetechnologiesinc.com. We aim to acknowledge accessibility reports within two business days and to tell you what we are going to do about it, and when.

Formal complaints

If our response does not resolve the issue, you may escalate it to our founder at the same address, marking the subject Accessibility escalation. We are small enough that this reaches a decision-maker directly, and we would rather hear it from you than from a complaint.