Accessibility Statement

Track Star EAM is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, which is the standard referenced by Section 508 of the Rehabilitation Act and by most state and local procurement rules in the United States.

We publish what we measured and how, rather than a claim on its own. Section 3 lists what is covered by testing, and section 4 lists what we know does not meet the standard today. A statement without those two sections is not worth reading.

• Every interactive control in the application carries an accessible name, so a screen reader announces what a button does rather than announcing the word "button". Controls in a list carry the name of the record they act on.
• Form fields are associated with their visible labels, so the label is both announced and clickable.
• Every screen is reachable and operable with a keyboard alone, including the dialogs, menus and tables.
• Text and interface colors meet the 4.5 to 1 and 3 to 1 contrast ratios in both the light and the dark theme.
• Images that carry information have text alternatives, and images that are decoration are hidden from assistive technology rather than announced as noise.

Two checks, and both fail rather than warn:

• A source-level check over the entire application that finds any control, field or image without an accessible name. It runs in the test suite on every change, so it covers every screen, including ones a browser test would not reach.
• An axe-core audit against WCAG 2.1 A and AA, run in a real browser against a production build, signed in as an administrator, over one screen from each module of the product plus the pages a visitor can reach.

Last run on October 14, 2026: eighteen screens, zero violations, in both the light and the dark theme.

Automated testing finds a large share of the defects that matter and it does not find all of them. It cannot judge whether a label is a useful description, whether a reading order makes sense, or whether a workflow is completable without sight. We are scheduling a manual audit with assistive technology users and will publish a dated Accessibility Conformance Report when it is complete.

• The map on the dashboard. Vehicle positions are drawn on a canvas and cannot be reached with a keyboard or read by a screen reader. Every asset shown on the map is also listed in the asset register with the same location information, which is the equivalent non-visual path.
• Charts. Chart graphics are not individually described. The data behind every chart is available as a table and as an export.
• Documents customers upload. We cannot make a PDF or an image uploaded by a customer accessible on their behalf.
• Manual testing is not finished. The conformance above rests on automated testing across all screens plus a browser audit of one screen per module. Manual screen reader testing of every workflow is in progress.

If any part of this product stops you doing your job, tell us and we will treat it as a defect, not a feature request. Say which screen, what you were trying to do, and what assistive technology you use.

Customers procuring under Section 508 may request our current Accessibility Conformance Report at the same address.