What it covers
It covers the public marketing site, public trust or legal pages, and other public-facing content linked from this website where the same site pattern is used.
This statement applies to the Pathway public website and related public-facing pages in this repository.
It is intended to explain our approach in plain English, set sensible expectations, and invite feedback where the site can be improved.
Unless clearly stated elsewhere, this statement does not apply to the Pathway application itself.
This accessibility statement applies to the Pathway public website and selected public-facing pages published from this website repository.
It covers the public marketing site, public trust or legal pages, and other public-facing content linked from this website where the same site pattern is used.
It does not automatically extend to the Pathway application or private customer environments unless those are explicitly documented separately.
We aim to make the public website easier to use by keeping its structure and presentation straightforward.
We aim to use headings, sections, and page structure that make content easier to follow.
We aim to keep wording plain, readable, and broken into shorter sections rather than long walls of text.
The public site is designed to adapt across desktop and mobile layouts so content remains usable on different screen sizes.
Navigation and links are intended to be usable by keyboard where supported by the site's current implementation.
We aim to choose text and interface colours with readability in mind across the site design.
Accessibility improvements are treated as an ongoing part of maintaining the public site rather than a one-off task.
We aim for the public website to be usable, but some areas may still need improvement.
If you experience an accessibility issue on the Pathway public website, or need information in another format, please get in touch using the available public contact route.
You can contact Pathway through the public website enquiry form or by email, and explain the issue you experienced or the information you need.
If possible, include the page you were using, what went wrong, and what would have helped so the issue can be understood more quickly.