1. Our commitment
As a WordPress development studio, accessibility is part of our own professional practice: we build accessible sites for clients, and we hold this site to the same standard. We aim for our pages to be perceivable, operable, understandable and robust for people using assistive technologies such as screen readers, voice control and keyboard-only navigation.
2. Conformance target
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. This is a widely recognised, internationally used standard for web accessibility. We treat it as a target we continually work towards rather than a one-off certification.
3. Measures we take
To support accessibility on this site, we:
- Use semantic HTML and landmark regions (header, nav, main, footer) so assistive technology can navigate the page structure.
- Provide a “skip to content” link at the start of every page.
- Maintain sufficient colour contrast and legible type sizes across the design system.
- Label form fields, buttons and links with clear, descriptive text.
- Test pages with automated tooling (including axe-core) as part of our development process, and fix issues this surfaces.
- Keep interactive components (menus, accordions, forms) operable by keyboard alone.
4. Known limitations
No website is perfectly accessible at every moment – content changes, and third-party embeds (such as code samples or social widgets) are outside our direct control. If you encounter a barrier, we want to know about it so we can fix it; see “Feedback and contact” below.
5. Feedback and contact
If you have trouble accessing any part of this site, or want to report an accessibility issue, please contact us at hello@hsrtech.com or via our contact page. Please include the page URL and a description of the issue, and the browser/assistive technology you were using where possible. We aim to respond within a few working days.
6. Technical information
This website is built on WordPress using a custom block theme. Accessibility testing has included automated auditing with axe-core across all page templates. This statement was last reviewed on 29 September 2026.
