Accessibility

GeoRoutes should be usable by everyone who needs to plan a round, including people using a keyboard alone, a screen reader, or magnification. We aim to meet the Web Content Accessibility Guidelines 2.2 at level AA.

We are not claiming full conformance, because we have not carried out the independent audit that such a claim requires. What we have done is run automated checks on every public page as part of our test suite, so that a serious or critical issue fails the build rather than shipping quietly.

Automated testing catches roughly a third of accessibility problems. It cannot tell whether a description is meaningful or whether a flow makes sense when read aloud. Treat a clean result as a floor rather than a guarantee.

• All content pages — home, pricing, how it works, the help guides and these policies — are plain semantic HTML with headings in order.
• A carer’s round is rendered on the server as a plain list with ordinary links, so it works before any JavaScript loads and reads sensibly on a phone with a screen reader.
• Colour is never the only way information is conveyed; times, labels and warnings are always written out as text.
• Text can be resized and the layout reflows down to a narrow phone screen without horizontal scrolling.
• Every interactive element shows a visible focus ring, and a “skip to main content” link appears on first tab so the navigation does not have to be traversed on every page.
• Each staff member’s round in the results list is a standard expand-and-collapse control, announcing whether it is open, with the round itself outside the button rather than nested inside it.
• A request for reduced motion is respected: animations and transitions are effectively disabled.

These are the barriers we are aware of. Naming them is more useful than a statement that implies there are none.

• The map is visual. Route lines and pins convey information that is only available by looking. The same schedule is always available as a text list alongside it, which is the accessible route through the same information.
• The feedback form is a third party. It is a Google Form embedded in the page, and its accessibility is Google’s rather than ours. If it causes difficulty, email us instead and we will treat that as equivalent.
• Drag interactions in the calendar have keyboard equivalents, but they are not yet documented anywhere obvious.

If something prevents you using GeoRoutes, please email support@georoutes.co.uk and describe what you were trying to do. Tell us which browser and assistive technology you use if you know. We will reply, and we will tell you plainly whether and when we can fix it.

If you need information from this site in another format, ask and we will provide it.

If you are not happy with our response, the Equality Advisory and Support Service (EASS) can advise you. GeoRoutes is a private business rather than a public sector body, so the Public Sector Bodies Accessibility Regulations 2018 do not apply to this site — but the Equality Act 2010 does, and we take it seriously.

See also our Privacy Policy, Security and Terms of Service.