Company page

Accessibility statement

Accessibility notes for the rebuilt PHP site.

This build aims for readable contrast, keyboard navigation, semantic headings, useful alt text, and image fallbacks when media is missing.

The layout is responsive and designed to avoid layout surprises on small screens. If you notice a barrier, the page can be updated as the site matures.

As the content library grows, we will keep checking colour contrast, focus states, and motion preferences so the experience stays usable for more people.

What we review

The site is reviewed for keyboard access, visible focus, heading order, colour contrast, readable text, useful link labels, responsive layouts, and alternative text where an image conveys information. Decorative marks should remain hidden from assistive technology when they add no meaning.

Report a barrier

When reporting an accessibility problem, include the page URL, device or browser, assistive technology if relevant, and the action that could not be completed. A precise report makes it possible to reproduce and correct the issue.

Keeping this page useful

Good reference pages should answer the immediate question and make the next step clear. Revisit this page when the publication adds a new section, changes a contact route, introduces a measurement tool, or updates its editorial practice. Keep dates, definitions, and links aligned with the current site so readers can tell what is current and what is historical.

The same standard applies across the desk: explain the subject plainly, avoid unsupported certainty, and give readers enough context to decide whether they need deeper research. A concise page can still be rigorous when its scope, audience, limitations, and practical use are visible.