Accessibility statement

We want everyone to be able to read and use milecall.com, whatever device, browser or assistive technology they use. We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA on this site, and we treat that as work that is never quite finished.

This statement is about the public website. The MileCall software (the web app, the driver app and the rider pages) is a separate product; customers can ask us about its accessibility directly.

Across the site:

• Keyboard. Every link, button, menu and form field can be reached and used with the keyboard. A “Skip to content” link is the first thing the Tab key lands on.
• Visible focus. The element the keyboard is on shows a clear outline, in both themes.
• Colour and contrast. Text colours are chosen for at least 4.5:1 contrast against their background in both the light and the dark theme, and colour is never the only way something is said.
• Motion. If your system asks for reduced motion, the animated product scenes stop and show their finished state, and nothing on the page moves on its own.
• Text alternatives. Each product scene has a written description for screen readers, and the facts it shows are also in the text beside it. Decorative shapes are hidden from assistive technology.
• Themes. The site follows your system’s light or dark setting, and the header lets you pick either one.
• Languages. The page for riders, caregivers and facility staff is available in English and in Spanish, each marked with its language so a screen reader pronounces it correctly.
• Structure. Each page has one main heading, headings in order, landmarks for the header, navigation, content and footer, and form fields with labels and inline error messages that screen readers announce.
• Small screens and zoom. Pages are built to reflow on narrow screens and at high zoom without sideways scrolling, and buttons are sized for fingers.

• The animated product scenes are illustrations of the software, not the software itself. A screen reader gets a description of each scene and the text next to it, but can’t step through the animation, and the small type inside a mocked-up window or phone isn’t meant to be read on its own.
• The maps are images of the Inland Empire drawn from OpenStreetMap. The place names and routes that matter are written beside them; the map itself can’t be explored.
• On a phone, some wide product windows scroll sideways so their content stays legible. That scroll works by touch, mouse or trackpad, not yet by keyboard; the same facts are in the text around the window.

If something on milecall.com is hard to use or doesn’t work with your assistive technology, please tell us at info@milecall.com. It helps to include:

• the address of the page,
• what you were trying to do and what happened instead,
• the browser and device you were using,
• any assistive technology you use, such as a screen reader or magnifier, and its version.

We aim to reply within five business days, and to fix what we can on the site. If you need something from a page in another form, say so and we’ll send it.

This statement was last updated on October 11, 2026. We review it when the site changes. It describes what we aim for and what we do; it isn’t a certification or a guarantee of conformance. The standard we work to is WCAG 2.1, published by the W3C.