Accessibility
How Loadara LLC works to make Loadara usable by everyone.
Our target
We aim for Loadara to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, across the website, the office workspace, the driver app and the links we send to customers, carriers and drivers.
Where we are
Loadara partially conforms to WCAG 2.1 AA: some content does not yet fully meet the standard. We have not had an independent audit. What we do today:
- Every change is checked by an automated scan (axe-core) before it can ship: the main website pages, and the main workspace and driver app pages in both light and dark mode, including the create forms that open as dialogs.
- The colour palettes of the workspace (both modes) and the website are tested for text contrast of at least 4.5:1 and input borders of at least 3:1.
- Our code is linted for common accessibility mistakes.
- Pages have descriptive titles; pages with navigation have a skip link to the main content; animations respect the reduced-motion setting.
Automated tools find only part of the problems people meet. Known gaps we are working on:
- Not every workspace page and dialog is covered by the automated scan yet, and the platform admin pages are not scanned.
- We have not yet completed full screen reader and keyboard-only testing of every workflow, including the dispatch board and the driver app.
- Some charts and maps do not yet offer an equivalent text or table view.
- Printed documents (invoices, settlements, rate confirmations) have not been reviewed as accessible PDFs.
Tell us about a barrier
If something in Loadara is hard or impossible for you to use, email system@loadara.com with the page and what happened. We will reply, and where we cannot fix it quickly we will help you get the information or complete the task another way.
Last updated: October 10, 2026
Questions: system@loadara.com · Loadara LLC, North Carolina