1. Our commitment
Tripkoz Technologies is committed to making Tripkoz usable by as many people as possible, including people who use screen readers, keyboard-only navigation, magnification, speech input, or who need reduced motion or higher contrast.
Accessibility is treated as part of building the product rather than as a later pass. Where we fall short, we would rather say so on this page than leave you to discover it.
2. The standard we measure against
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA for the Tripkoz website and web dashboard.
We also take account of the Rights of Persons with Disabilities Act, 2016 and the Guidelines for Indian Government Websites where they apply to a service used by schools and public institutions.
Current status: partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the Service meets the standard, and the known exceptions are listed in section 5.
3. What this statement covers
This statement applies to:
- The Tripkoz marketing website at www.tripkoz.com;
- The Tripkoz web dashboard used by organisation administrators and super administrators.
The Tripkoz Android application is assessed separately against the Android accessibility guidelines and is not covered by this statement. Third-party components embedded in our pages — the Razorpay checkout window and Google Maps in particular — are controlled by those providers and are outside our conformance claim, though we choose accessible alternatives where they exist.
4. What already works
Across the website and dashboard:
- Keyboard navigation — every interactive control is reachable and operable by keyboard, with a visible focus ring. A "Skip to main content" link is the first thing a keyboard or screen-reader user reaches on every page;
- Semantic structure — pages use real headings in order, landmark regions, lists and tables, so a screen reader can move by structure rather than line by line;
- Labels and names — form fields have associated labels, icon-only buttons carry accessible names, and errors are announced rather than shown only in red;
- Colour and contrast — text and interface elements are checked against the 4.5:1 (and 3:1 for large text) contrast ratios in both light and dark themes. Colour is never the only way information is conveyed: statuses carry text and shape as well;
- Dark mode and zoom — the interface reflows at 200% zoom and down to a 320px viewport without loss of content or horizontal scrolling;
- Reduced motion — animations respect the prefers-reduced-motion setting, and no content flashes more than three times per second;
- Timeouts — the 15-minute inactivity sign-out warns before it acts, and the session can be extended.
5. Known limitations
We know about the following, and each is on our plan to fix:
- Live map views — the vehicle map is inherently visual. Positions are also available as text in the trip and vehicle lists, but the map itself is not fully usable by screen reader. We are extending the text alternative to cover live position and ETA;
- Complex data tables — some administrative tables with many columns require horizontal scrolling at high zoom;
- Charts — dashboard charts convey trends visually; the underlying figures are available in the adjacent summary cards, but not yet as a table alternative for every chart;
- Third-party checkout — the Razorpay payment window is rendered by Razorpay and its accessibility is theirs. If you cannot complete a payment because of it, contact us and we will take the payment another way;
- PDF invoices — generated invoices are not yet tagged for screen readers. On request we will send the same information in an accessible format.
6. Compatibility
The Service is designed to work with recent versions of:
- Screen readers — NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android;
- Browsers — Chrome, Edge, Firefox and Safari, each on its current and previous major version;
- Operating-system features — magnification, high-contrast modes, and browser text resizing.
The Service may not work well with browsers more than two major versions old, or with assistive technology that no longer receives updates.
7. How we assess it
We use a combination of automated and manual testing: automated checks in development, manual keyboard-only passes on new screens, screen-reader spot checks on the flows that matter most (sign-in, billing, adding a driver or vehicle, reading a trip), and contrast checking of the design tokens in both themes.
This statement was last reviewed on the effective date shown above. We review it whenever a significant part of the interface changes, and at least once a year.
8. Feedback and how to reach us
If something on Tripkoz is difficult or impossible to use, please tell us at accessibility@tripkoz.com. Include the page or screen, what you were trying to do, and the browser and assistive technology you were using if you know them.
We acknowledge accessibility reports within two (2) business days. Where a fix will take time, we will offer a workaround or complete the task with you in the meantime, at no charge.
If you are not satisfied with our response, you can escalate to our Grievance Officer at grievance@tripkoz.com, who acknowledges within 24 hours and aims to resolve within 15 days.
Related policies
This document sits alongside the rest of our published terms. Together they form the agreement that governs your use of Tripkoz.