Home / Accessibility

Accessibility statement for Milepost

How accessible the Milepost dashboard and app are, what we know is not yet right, and how to tell us.

Last reviewed: 6 October 2026

This accessibility statement applies to:

  • the Milepost Hub web dashboard at app.milepost.civildigital.co.uk, including the public sign-up, join, password-reset and account-deletion pages;
  • the Milepost Android app, in both its Hub and Tracker roles.

It does not cover this marketing website, which will have its own statement.

Milepost is run by Civil Digital. We want as many people as possible to be able to use it. For example, that means you should be able to:

  • change colours, contrast levels and fonts using your browser or device settings;
  • zoom in up to 400% on the web dashboard without text spilling off the screen, and use the Android app with the largest system font size;
  • use the whole web dashboard with a keyboard alone, including placing a zone without a mouse;
  • navigate the web dashboard with a screen reader (headings, landmarks, labelled controls, a “Skip to content” link, and dialogs that announce themselves and keep your place);
  • use the Android app with TalkBack: every switch, button and field is named, and titles are marked as headings;
  • rotate the Android app to either orientation.

We have also tried to make the text as simple as possible to understand.

How accessible Milepost is

We know some parts are not fully accessible:

  • The maps. The live map, route history map and zone map are drawn by Google Maps, which is not fully accessible to screen readers or by keyboard. The same information is available without the map:
    • the Devices list (web and app) gives each person’s status, the age of their last position, speed and battery;
    • Route history states the time range and the distance and point statistics, and can be exported as a CSV file with every position, time and speed;
    • a zone’s centre can be typed or pasted as latitude and longitude, or taken from a person’s current position, instead of clicking the map.
  • PDF files in Messages are shown as page images, so a screen reader can’t read their text inside Milepost. Use Download in the viewer: the file opens in your own PDF app, which can read it aloud. On the web dashboard this is fixed in our October 2026 release, which puts the real text over each page.
  • Scanned PDFs contain pictures of text rather than text. Download the file to use a tool that can recognise it.
  • Videos in Messages are uploaded by your colleagues, and Milepost cannot add captions to them.
  • Photos in Messages have the file name as their only text alternative, because they are shared by users rather than written by us.
  • Map pins on Android show a person’s status and age as a picture. The same facts are in the pin’s description and in the Devices list.
  • Some names are shortened with “…” on narrow screens (the live-map device list and the chat list on the web). Our October 2026 release lets them wrap onto a second line instead.

Feedback and contact information

If you need information from Milepost in a different format, such as accessible PDF, large print, easy read or audio:

We’ll consider your request and get back to you within 5 working days.

Reporting accessibility problems

We’re always looking to improve the accessibility of Milepost. If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, email info@civildigital.co.uk or call 07568 296136. Please tell us the page or screen, the device and browser, and any assistive technology you were using.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010 in England, Scotland and Wales. If your organisation buys Milepost as a public sector body, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 may also apply to your use of it. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS). In Northern Ireland, contact the Equality Commission for Northern Ireland.

Technical information about Milepost’s accessibility

Civil Digital is committed to making Milepost accessible, in line with the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. For the Android app we apply WCAG 2.2 AA as EN 301 549 and the W3C’s WCAG2ICT guidance apply it to mobile software.

Compliance status

Milepost is partially compliant with WCAG 2.2 level AA, due to the non-compliances and exemptions listed below.

Non-accessible content

Non-compliance with the accessibility regulations

  1. Maps (all three) can’t be operated or read in full with a screen reader or keyboard alone. This fails WCAG 1.1.1 (non-text content) and 2.1.1 (keyboard) for the map canvas itself. Equivalent routes exist, as described above. We are looking at a text list of positions under the route history map, and at giving map pins keyboard focus on the web.
  2. PDF pages in Messages are drawn as images with no text layer, so their text is not available to screen readers inside Milepost. This fails WCAG 1.1.1 and 1.3.1 for the in-app viewer. The viewer’s Download button saves the file, where it opens in the user’s own PDF app; downloads are recorded for the organisation’s Hubs, as for every file. The web dashboard’s viewer gains a text layer in our October 2026 release.
  3. Shortened names in the web dashboard’s live-map device list and chat list hide the full name at 320 pixels wide and 400% zoom (WCAG 1.4.10). Fixed in our October 2026 release.

We will review this list by 31 March 2027, or sooner if any of it is fixed.

Content that’s not within the scope of the accessibility regulations

  • User-generated content: photos, videos, documents and message text sent by users of an organisation, including scanned PDFs that contain no text. Milepost can’t caption or describe these for them.
  • Third-party content: Google Maps map tiles and controls, which Civil Digital does not develop or control.

What we’re doing to improve accessibility

On 30 September 2026 we audited Milepost against WCAG 2.2 AA and fixed what we found, including:

  • Colour contrast: every text and colour pair now meets 4.5:1; the orange call-to-action buttons and the green and amber status text were darkened; avatar initials pick dark or white text by contrast.
  • Keyboard: a Skip to content link; dialogs that take focus, keep it, close with Escape and return you to where you were; arrow-key menus; keyboard zoom and pan for photos; a keyboard way to place a zone.
  • Screen readers: headings and landmarks on every page; every view has its own page title; labels on all form fields; errors and new alerts are announced; selected states (filters, chips, colour choices) are exposed as well as shown with a tick; colour swatches have names.
  • Touch and pointer: no control smaller than 24 × 24 pixels on the web; Android controls use the standard 48dp touch size, including the group colour picker, which used to be 14dp; Reply is a visible button on touch screens, not only a swipe.
  • Android: headings on every screen; switches and checkboxes named by their labels; status shown in words as well as colour; confirmation before clearing alerts; PDF zoom buttons; TalkBack actions for Reply and Delete on messages; positions shown as text as well as on the map.

Our October 2026 release adds a text layer to PDFs on the web dashboard, so a screen reader can read their text and you can select and copy it; lets names wrap instead of being shortened; and links to this statement from every page of the dashboard.

We test every release with automated checks (axe-core). We have not yet booked an independent audit; we will name the auditor and the date here once we have.

What we still need to test

The fixes above were checked with automated tools, with scripted keyboard tests in a real browser, and by code review. We have not yet completed a full session with each of these assistive technologies, and we will update this statement when we have:

  • NVDA with Chrome;
  • VoiceOver with Safari;
  • TalkBack on a physical Android phone;
  • Switch Access on Android.

Preparation of this accessibility statement

This statement was prepared on 30 September 2026. It was last reviewed on 6 October 2026.

Milepost was last tested on 5 October 2026 against the WCAG 2.2 AA standard. The test was carried out by Civil Digital. It covered:

  • every page of the web dashboard, its dialogs and its public pages, at 1440px, 390px and 320px wide;
  • every screen of the Android app, by code review, with the build, unit tests and Android Lint passing. Tracker screens were also checked on an Android emulator by reading their accessibility tree.