Accessibility statement
How this website aims to meet accessibility standards, and what to do if something does not work for you.
Last updated: 1 October 2026
Our commitment
We want this website to be usable by as many people as possible, including those using screen readers, keyboard-only navigation, magnification or reduced-motion settings.
What we have done
- Semantic HTML structure with a logical heading order
- A skip link to the main content on every page
- Text contrast that meets WCAG 2.2 AA for body copy
- Keyboard-operable navigation with visible focus states
- No content that depends solely on colour to convey meaning
- Layouts that reflow without horizontal scrolling at 320px width
- Body text that remains readable when zoomed to 200%
- No autoplaying media, animation loops or motion that cannot be avoided
- Descriptive page titles and language declared as English (United Kingdom)
Known limitations
- Some older case study documents referenced from this site may not be fully tagged. We will provide an accessible version on request.
- The expandable question sections rely on native browser behaviour. Where a browser does not support this, all content remains visible by default.
Standards we aim for
We work to Web Content Accessibility Guidelines (WCAG) 2.2 level AA. This site has not been formally audited by a third party; the measures above reflect our own testing with keyboard navigation, screen reader spot checks and browser zoom.
Getting help
If you need information from this site in a different format — large print, plain text, or as an audio recording — email sophia.carter@azkoro.com and we will provide it, usually within five working days.
Reporting a problem
If you find something on this site that does not work with your setup, tell us at sophia.carter@azkoro.com. Include the page and a description of what happened. We treat accessibility reports as bugs and aim to fix them promptly.