Built to be used
by everyone.

FleetPath is built for people who run trucking operations, and those people work in every condition and with every ability. We are committed to making our web application and iOS application usable by everyone, including people who rely on keyboards, screen readers, screen magnification, high-contrast modes, or reduced-motion settings.

We treat accessibility as an ongoing engineering practice, not a one-time checkbox. As we build new surfaces, we test them for accessibility, and we return to older surfaces to raise them to the same bar. This statement describes where that work stands today and how to tell us where it falls short.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG is the internationally recognized reference for accessible digital products, and Level AA is the level most organizations aim for. In plain terms, the guidelines ask that content be:

• Perceivable. Information is presented in ways people can perceive, for example text alternatives for images and sufficient color contrast.
• Operable. Every control can be reached and used, including with a keyboard alone, and users can see where they are.
• Understandable. Text is readable, and the interface behaves in predictable ways.
• Robust. Content works with assistive technologies such as screen readers.

We use WCAG 2.1 AA as the goal we design and test against. We are honest that this is a target we work toward continuously. We do not claim that FleetPath has completed a certified conformance audit against every success criterion, and we have not published a Voluntary Product Accessibility Template. When our testing surfaces a gap against the standard, we treat closing it as normal product work.

The following practices are in place across our marketing site and product surfaces today:

Semantic structure

Pages are built with meaningful HTML: real headings, landmarks, lists, and buttons rather than generic containers. This gives screen readers and other assistive technologies an accurate outline of each page so users can navigate by structure.

Descriptive labels and alt text

Interactive controls carry descriptive, human-readable labels, and meaningful images carry alternative text that conveys their purpose. Decorative imagery is marked so assistive technology can skip it.

Full keyboard navigation

Interactive elements can be reached and operated with the keyboard alone, without requiring a mouse or touch. Navigation follows a logical order through the page.

Visible keyboard focus

When you move through a page with the keyboard, a visible focus indicator shows which element is currently active. We recently added clear, consistent focus styling across the marketing site so keyboard users never lose their place.

Sufficient color contrast

Our light editorial design is built for readable contrast between text and its background, so content stays legible for users with low vision and in bright environments such as a truck cab in daylight.

Text that reflows and scales

Layouts are responsive. Text reflows and remains readable when you zoom in or increase your default font size, without content being cut off or overlapping.

Motion that respects your settings

We honor the operating-system reduced-motion preference. If you have asked your device to reduce motion, animations and transitions are disabled so the interface does not move in ways that can cause discomfort.

Being honest about accessibility means naming where we are not yet where we want to be. Some current limitations:

• Third-party embedded content. Some features rely on embedded content such as interactive maps. The accessibility of that content depends in part on the provider, and it may have gaps we do not fully control. Where we can, we provide an accessible alternative path to the same information.
• Coverage is not uniform. Newer surfaces are built to our current bar. Older surfaces are being brought up to the same level over time, so you may encounter areas that are further along than others.
• Testing is continuous, not certified. We test with automated tools, manual keyboard checks, and assistive technology, and we improve on a rolling basis. We have not completed a formal, certified third-party conformance audit, and we do not represent our testing as one.

We prioritize accessibility issues alongside other product work and give barriers that block someone from completing a task the highest priority.

If you run into a barrier anywhere in FleetPath, we want to hear about it. Email admin@fleetpath.app and, if you can, include:

• The page or screen where you hit the problem.
• What you were trying to do.
• The assistive technology, browser, or device you were using, if relevant.
• What happened, and what you expected instead.

You do not need to use any special format or technical language. A short description of what got in your way is enough for us to investigate. We aim to acknowledge accessibility reports promptly and to follow up with the steps we are taking to address them.

Reports of barriers feed directly into how we prioritize this work. When you tell us about a problem, we investigate it, fix what we can, and use what we learn to prevent the same issue elsewhere. Accessible design gets easier the earlier we catch it, and your feedback is the most direct signal we have.

We update this statement as our practices improve. If you have feedback on the statement itself, or on how we can make FleetPath work better for you, reach us at admin@fleetpath.app.