Accessibility statement for PaxCast

Last updated: 1 November 2026

This statement applies to the PaxCast application, the PaxCast product pages and the documents PaxCast produces. PaxCast is provided by Infin8 Digital Limited.

We want as many people as possible to be able to use PaxCast. For example, you should be able to:

• zoom in up to 400% without the text spilling off the screen
• navigate most of the application using just a keyboard
• use most of the application with a screen reader
• use PaxCast on a phone or tablet as well as a computer
• turn off moving vehicles on the map

We have also tried to make the text easy to understand. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible PaxCast is

PaxCast is mainly a map, and some parts are harder to use without seeing it. We know that:

• documents downloaded as PDF are not tagged for screen readers (each one is also available as a Word document, which is the accessible version)
• some charts and maps rely on colour, and on the light map style some types of service are told apart by colour alone
• the single-key keyboard shortcuts cannot be turned off or changed
• moving vehicles can only be paused using the Vehicles switch in the side menu
• some map features, including drawing and adjusting a route, are easier with a mouse or touch than a keyboard
• PowerPoint slide packs do not use slide title placeholders, so slide titles may not be announced
• some specialist tools, including the snapshot tool, the 3D view and the field tools, have not been fully tested for accessibility

Feedback and contact information

If you need information from PaxCast in a different format, such as an accessible document, large print or plain text, email contact@infin8.digital. Tell us what you need and how you would like to receive it. We will reply within 10 working days.

Reporting accessibility problems

We are always looking to improve the accessibility of PaxCast. If you find a problem not listed on this page, or you think we are not meeting accessibility requirements, email contact@infin8.digital or use the Feedback button in the application.

Enforcement procedure

In Great Britain, the Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are 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 PaxCast's accessibility

Infin8 Digital Limited is committed to making PaxCast accessible. Public bodies using PaxCast must meet the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, and we design PaxCast to help them do so.

Compliance status

PaxCast is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed below.

Non-accessible content

Non-compliance with the accessibility regulations

• Documents in PDF format are not tagged, so headings, tables and reading order are not available to screen readers. This fails WCAG 1.3.1 (Info and relationships). Every report is also available as a Word document and an Excel workbook, which carry their structure. We plan to tag PDFs by 30 January 2027.
• Colour. On the light map style, some types of service, and some chart and map keys, are told apart by colour alone. This fails WCAG 1.4.1 (Use of colour). Line numbers, labels and the information boxes give the same information in text. We plan to fix this by 30 January 2027.
• Keyboard shortcuts. Single-key shortcuts on the map cannot be turned off or changed. They act only when you are not typing in a text field. This fails WCAG 2.1.4 (Character key shortcuts). We plan to fix this by 30 January 2027.
• Drawing routes. Placing and dragging route points is designed mainly for a pointer. Keyboard alternatives exist: each calling point has a menu with options to move it with the arrow keys, and Enter on the map adds or opens what is at the centre of the view. Some drawing tasks still take much more effort without a pointer. This may fail WCAG 2.1.1 (Keyboard) and 2.5.7 (Dragging movements). We plan to fix this by 30 January 2027.
• Slide packs. PowerPoint slides do not use title placeholders, so screen readers may not announce slide titles. This fails WCAG 2.4.2 (Page titled) as applied to documents. We plan to fix this by 30 January 2027.
• Specialist tools. The snapshot tool, the 3D view, the Field Counter and Path Finder have not been fully tested and may contain further failures. We plan to test and fix them by 30 January 2027.

Disproportionate burden

We are not claiming disproportionate burden for any part of PaxCast.

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

Maps. The regulations do not require online maps to be accessible, as long as essential information is provided in an accessible format. In PaxCast, the information shown on the map (stops, routes, areas and their figures) is also available in text in the information boxes, the search results and the reports.

What we're doing to improve accessibility

We review PaxCast against WCAG 2.2 AA when we make changes, and we fix the problems listed above in priority order. Recent improvements include keyboard access to everything that can be opened on the map, focus returning to where you were when a panel closes, announcements of finished reports for screen readers, reduced motion when your device asks for it, and larger touch targets.

Preparation of this statement

This statement was prepared on 1 November 2026. It was last reviewed on 1 November 2026.

PaxCast was last tested on 24 October 2026. The test was carried out by Infin8 Digital Limited as a self-assessment against WCAG 2.2 AA.