Accessibility statement

We want as many people as possible to be able to use them.

In the apps, you should be able to

• change your device's text size and have the app's text resize with it;
• use your device's screen reader (VoiceOver on iOS, TalkBack on Android);
• navigate the app with assistive technologies;
• use the app in your device's high-contrast or dark mode.

In the Station Dashboard, you should be able to

• zoom in up to 200% with your browser, and have the dashboard redraw at the larger size;
• use it in your device's light or dark appearance, which it follows automatically;
• use a screen reader: the dashboard's screen-reader support is on from the moment it opens;
• read availability as numbers as well as colours: the planner shows each person's planned hours, and crewing shortfalls as counts.

On the crew board, you should be able to

• read whether the station is ready in words (for example “Ready to respond” or “Need 1 more Driver”), not only from its colour;
• read each person's status as text beside their coloured marker, and the number on call in each role as a count;
• during a callout, see how many people are responding, delayed and on scene as labelled counts, and each responder's status as text;
• choose a dark or light theme with the switch on the board, or set one in the board's link.

AbilityNet has advice on making your device easier to use if you have a disability.

The apps

• Colour used to convey status. Some information, such as availability and on-call status, is shown mainly through colour. In the Edit availability screen, for example, each hour in the grid shows its status only by its colour; the summary above the grid gives the hours for each status in words, and screen readers announce each hour's status. We are adding text and shape cues so the meaning does not depend on colour alone.
• Screen-reader labels. Some buttons and controls that use icons may not be announced clearly by VoiceOver or TalkBack. We are adding descriptive labels.
• Tap target size. Some controls may be smaller than the recommended minimum size, which can make them harder to tap accurately.
• Maps. The maps use third-party components (Apple Maps and Google Maps) whose controls can be difficult to use with some assistive technologies.

The Station Dashboard

• Screen-reader labels. The dashboard draws its screens itself and builds a separate, accessible version of each screen for screen readers. Some controls may not yet be announced as clearly as they should be.
• Keyboard. Some controls, including parts of the availability planner and the maps, may not be usable with a keyboard alone.
• Not on phones. The dashboard is not available on phone-sized screens, so its content does not reflow to a narrow width. Crew can do the same everyday tasks in the iFire, iCrew or iRescue app.
• Text settings. Because text is drawn rather than set as web page text, browser text-only resizing, custom text spacing, find-in-page and translation extensions do not work on it. Browser zoom does.
• Charts. The overview charts show their numbers on screen, but the charts themselves are not described to screen readers.
• Maps. The en-route tracker and the hydrants and defibrillators map use Google Maps, whose controls can be difficult to use with some assistive technologies. The tracker also lists each responder and their distance beside the map.

The crew board

• Made to be watched, not used. The board is designed for a TV on a wall. It scales itself to fill the screen, so browser zoom and text-size settings do not make its text larger, and its content does not reflow for small screens.
• Live changes are not announced. The board updates by itself when anyone's status changes, but screen readers are not told about the change.
• Colour. Readiness and each person's status are colour-coded. The words and counts beside them carry the same information, but the coloured ring around each photo, and the colour of each pin on the map, which shows whether that person is responding or delayed, have no text of their own.
• Map. On screens a station has paired, the responders map is drawn with Leaflet and OpenStreetMap. It cannot be moved or zoomed with a keyboard, and responders' distances and estimated times are shown only on the map. The list of responders beside it gives their names and status.

We are always looking to improve accessibility. If you find a problem that isn't listed here, or you need information in a different format, please contact us:

Email: hello@ifireapp.org

We aim to respond within 5 working days.

iOnCall is not a public sector body, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the “accessibility regulations”) do not apply to us directly. We follow the same approach anyway, because many of the services that rely on iFire, iCrew and iRescue are public bodies.

As a service provider we have duties under the Equality Act 2010, or the Disability Discrimination Act 1995 in Northern Ireland. 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.

We are committed to making the apps and the Station Dashboard accessible, and we measure them against the same standard the accessibility regulations use.

Compliance status: the apps and the Station Dashboard are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed above.

We do not currently claim that any part of them would be a disproportionate burden to make accessible.

We have scheduled an independent WCAG 2.2 AA audit of the apps and the Station Dashboard. The issues it identifies will be prioritised and fixed, with automated accessibility checks added to our tests so that fixes don't regress. We will update this statement as issues are resolved.

This statement was first prepared on 31 May 2026 for the apps, updated on 10 October 2026 to cover the Station Dashboard, and on 12 October 2026 to cover the crew board. It is based on a self-assessment carried out internally. It will be reviewed following the independent audit, and at least once a year.