Accessibility statement

Using Path

Path is run by Michael Rowe. I want as many people as possible to be able to use it, whatever device or assistive technology they use. You should be able to:

• switch between light and dark themes, or change colours and fonts using your browser or device settings
• move through the site using just a keyboard

I've also tried to keep the text plain and easy to follow.

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

How accessible Path is

Some parts of Path haven't been checked yet. In particular, I haven't tested it with a screen reader, or checked every page at 200% zoom.

Feedback and contact information

If you find any part of Path hard to use, or need information in a different format, tell me through the contact page. I aim to reply within five working days.

If you're not happy with my response, you can contact the Equality Advisory and Support Service (EASS).

Compliance status

Path aims to meet the Web Content Accessibility Guidelines version 2.2 at level AA. It is partially compliant with that standard, because of the gaps listed below.

Non-accessible content

I haven't yet tested Path with a screen reader. It's built to follow the accessibility guidelines and checked with automated tools, but some things can only be confirmed with screen-reading software such as VoiceOver or NVDA: the order content is announced in, for example, or how well an image description reads in context.

I haven't yet checked every page at 200% zoom or on a screen 320 pixels wide. The layout is designed to reflow, but I haven't confirmed it across the whole site.

What I'm doing to improve accessibility

I'm working towards full conformance with WCAG 2.2 at level AA. That means closing the two gaps above: confirming Path works with screen-reading software, and that every page reflows at 200% zoom and on a screen 320 pixels wide. Once Path is used at a larger scale, I'll ask for an independent accessibility review.

Preparation of this statement

This statement was prepared on 23 October 2026. It was last reviewed on 24 October 2026.

It's based on my own assessment of Path against WCAG 2.2 at level AA. I'll update it when either of the gaps above is closed, or when a change to Path affects how accessible it is.