Accessibility Statement

1. Our Commitment

MileClear is built so UK drivers can claim every tax-deductible mile they're owed. That commitment only means something if the app works for everyone, regardless of how they use their phone or computer.

We aim to meet the international standard for accessible digital products on the web, and to follow Apple's accessibility APIs on iOS so the mobile app works with VoiceOver, Dynamic Type, Reduce Motion, increased contrast, and Switch Control.

We are not a large company with a dedicated accessibility team. We are one developer (Anthony) building MileClear for the UK gig and self-employed driving community. Where we fall short, we want to know - and we commit to fixing it.

2. The Standard We Aim For

Web: Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This is the standard the UK Public Sector Bodies Accessibility Regulations 2018 require of public-sector websites, and it's the same bar we hold ourselves to.

iOS: Apple's Human Interface Guidelines for Accessibility, which align with WCAG 2.1 AA at the platform level. Every interactive element in the app exposes a label and role to VoiceOver, and the UI adapts to system-level Dynamic Type, Reduce Motion, and Increase Contrast settings.

We have not yet commissioned a formal third-party accessibility audit. We do test against the standards above ourselves, and we treat every accessibility issue reported by users as a high-priority bug.

3. Web (mileclear.com)

The mileclear.com site and the web dashboard at mileclear.com/dashboard are designed to be usable with:

• Screen readers (VoiceOver, NVDA, JAWS, TalkBack via Chrome).
• Keyboard-only navigation. Every interactive element is reachable by Tab, and the visible focus ring is preserved across all components.
• Browser zoom up to 200% without horizontal scrolling or content loss.
• High-contrast mode and forced-colors mode in supported browsers.

We use semantic HTML throughout (headings in proper hierarchy, form fields with associated labels, lists for list content, ARIA only where native semantics aren't enough). Our colour palette - amber accent on dark navy - is checked against WCAG 4.5:1 contrast for body text and 3:1 for large text.

Decorative images carry empty alt attributes; informative images carry descriptive alt text. Embedded media is captioned where present (currently none).

4. iOS App

The MileClear iOS app supports:

• VoiceOver: Every button, list row, form field, toggle, and chart cell exposes an accessibility label and role. The Lock Screen Live Activity announces trip status changes.
• Dynamic Type: Text scales with the system font-size setting up to the largest accessibility size, without truncation or layout breakage.
• Reduce Motion: Decorative animations (skeleton loaders, transitions, the pulse on the Tax Readiness card) are disabled when Reduce Motion is on.
• Increase Contrast: Border and text colour weights increase when the system Increase Contrast setting is on.
• Switch Control: All interactive elements are reachable via Switch Control's group/sequential navigation.
• Smart Invert and Differentiate Without Colour: Information is never conveyed by colour alone (every coloured status pill also carries a label or icon).

We use Apple's on-device APIs for receipt OCR and Live Activities. Both are designed by Apple to work with assistive technologies and we do not interfere with that.

5. Known Limitations

We are honest about where we may fall short. As of the date at the top of this page:

• We have not commissioned a formal third-party WCAG 2.1 AA audit. We rely on self-testing with Lighthouse, axe, and manual VoiceOver / NVDA passes.
• Some chart and map visualisations (the Activity Heatmap, the trip-route map preview) provide aggregated text alternatives but do not yet expose every individual data point to screen readers.
• The Working Calendar on the web dashboard exposes day cells as links; multi-day range selection by keyboard isn't yet supported (single-day drill-through works).
• Some animations in the onboarding flow use opacity-only transitions; while these respect Reduce Motion, the static fallback can be slightly less inviting.

Each of these is on the development roadmap. If any of them blocks you from using MileClear, please report it (see below) and we'll prioritise.

6. Report an Accessibility Issue

If you find anything in MileClear that doesn't work with the assistive technology you use, we want to know.

Our promise: we'll acknowledge your report within 2 working days. We aim to ship a fix within 14 days for issues that block use of a feature, and within 30 days for everything else. If a fix takes longer because the underlying platform constrains us (rare but possible), we'll tell you what the timeline looks like and what we're doing in the meantime.

Anthony reads every accessibility report personally.

7. Enforcement

If you contact us about an accessibility issue and you're unhappy with our response, you can escalate to the Equality Advisory and Support Service (EASS):

• Web: equalityadvisoryservice.com
• Telephone: 0808 800 0082
• Textphone: 0808 800 0084

MileClear is a private commercial service, not a public-sector body, so we sit outside the Public Sector Bodies Accessibility Regulations 2018. We hold ourselves to the same standard regardless.