Accessibility · reviewed September 5, 2026

Accessible fleet work, wherever your team works.

FleetTrestle is built with responsive layouts, semantic structure, keyboard-accessible navigation, readable contrast, and programmatic labels as baseline requirements. This statement describes our current engineering and QA scope; it does not claim independent certification or perfect conformance with every WCAG success criterion.

Current testing scope.

⌨

Keyboard and focus

Hosted browser tests exercise shared navigation and critical interactive controls without relying only on pointer input.

Aa

Structure and contrast

Automated accessibility audits, semantic headings, labels, and design-system contrast checks are part of release quality work.

◎

Multiple widths

Public and authenticated surfaces are exercised at desktop, tablet, and mobile widths to catch responsive barriers and inaccessible layout changes.

Automated checks cannot prove full accessibility. Manual review and customer-reported barriers remain important, especially for assistive-technology behavior that automation cannot fully evaluate.

Encountered an accessibility barrier?

Tell us the page, task, assistive technology or input method involved, and what prevented completion. Accessibility issues are treated as product defects.

Report an accessibility issue →