Accessibility statement

What this covers

This statement applies to the TXC Toolkit, an internal web application for managing bus service data. It's used by staff at [organisation] and by invited bus operators. It does not cover the files the tool exports, or any other website.

How accessible this tool is

We've built it to be usable in the ordinary ways:

• every page is plain HTML with real headings, labels and tables — there's no JavaScript framework rendering the interface, so it degrades gracefully;
• everything except the maps can be operated by keyboard alone;
• text resizes and the layout reflows down to a narrow window;
• forms have labels tied to their fields, and errors are announced rather than only coloured;
• colour is never the only way information is given — statuses carry text as well.

We know some parts are not accessible enough, and they're listed below rather than glossed over.

Known problems

• The maps can't be used with a keyboard or a screen reader. The route and document maps are an interactive canvas: panning, zooming and clicking a stop marker all need a pointer. There is an equivalent way to do the same work — every stop can be found and added from the search box on the route page, and the stop list gives the same information as a table. No task requires the map.
• Wide data tables scroll sideways. On a narrow screen some tables have to be scrolled horizontally to reach the last columns. The scroll region is reachable by keyboard, but it's awkward.
• PDF timetable exports are probably not accessible. They're generated from HTML and we haven't verified the tagging, reading order or table headers in the output. The same timetable is available as a web page, which is the accessible route to the same information.
• The month calendar grid is dense. It conveys version overlaps largely through colour and position; the same dates are listed in text on the versions page.
• Tooltip text is not read out. The small explanations that appear when you hover or tab onto a button are drawn by the stylesheet, so a screen reader doesn't announce them. Buttons carry their own labels, so nothing is unusable without the tooltip, but the extra explanation isn't available.

Compliance status

This tool is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the problems listed above.

The relevant failures are: 2.1.1 Keyboard and 1.1.1 Non-text Content (the maps), and — pending testing — the PDF exports. [To be confirmed by formal testing.]

How this was tested

It has not been audited by an external organisation, and it has not been tested with assistive technology by disabled users. What's above comes from the developers' own review of the pages against WCAG 2.2 AA. Arranging a proper audit is [owner and target date].

Feedback and reporting problems

If you find a problem, or need something here in a different format, contact [accessibility contact — email address]. We aim to reply within [response time].

If you contact us and you're not happy with the response, the Equality Advisory and Support Service (EASS) can help: equalityadvisoryservice.com.

The Equality and Human Rights Commission enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

What we're doing about it

• Keep every map-based action reachable without the map — this holds today and is treated as a rule for new features, not an aspiration.
• Test the exported PDFs properly and fix the tagging, or say plainly that the web timetable is the accessible version.
• Get an external audit before the tool is opened to a wider group of users.

Preparation

This statement was prepared on 02 August 2026 and has not yet been reviewed by [accessibility lead].