Legal
Accessibility statement
We build for accessibility as a design constraint rather than a pre-launch audit. This statement sets out our target, how the site was tested, and what to do if something does not work for you.
Last updated
Pending review. This document is a working draft prepared during implementation. It must be reviewed and approved by the business owner or an appropriate legal adviser, and the registered entity name confirmed, before public launch.
Our target
This website is built to meet WCAG 2.2 level AA. That target applies to the whole public site, including the contact form and the navigation.
What this means in practice
- Semantic landmarks for the header, navigation, main content, and footer
- A skip link to main content, visible when it receives keyboard focus
- Every interactive element reachable and operable by keyboard, with no keyboard traps
- A visible focus indicator with sufficient contrast on every focusable element
- Menus and accordions that expose their state programmatically and close on Escape
- Form labels that are always visible, with errors tied to the field they describe
- An error summary that receives focus when a submission fails, and a live region for status
- Meaningful alternative text on informative images and empty alt text on decorative ones
- Colour never used as the only way of conveying information
- Layouts that work at 200% zoom and down to a 320 pixel viewport without horizontal scrolling
- Touch targets sized for comfortable use on small screens
- Motion kept subtle and disabled when your system requests reduced motion
How this site was tested
Testing during implementation included:
- Automated axe checks running against representative pages in the build pipeline
- Lighthouse accessibility audits
- A keyboard-only walkthrough of the primary journeys, including the contact form
- Screen reader spot checks
- Review at 200% browser zoom and at narrow viewport widths
- Review with reduced-motion enabled
Automated tools catch only a portion of accessibility issues, so manual review is part of our release process rather than an optional extra.
Known limitations
We are not aware of any WCAG 2.2 AA failures at the time of writing. Where an issue is identified after launch, we will list it here along with the planned remediation, rather than removing the statement.
The logo used on this site is supplied as a raster image pending an approved vector master. It has appropriate alternative text and scales correctly, but a vector version will improve rendering at high zoom levels.
Third-party content
Microsoft Clarity is used for behaviour analytics. It does not add interface elements to the page and the site remains fully usable if it fails to load or is blocked.
Tell us about a problem
If any part of this site is difficult or impossible for you to use, please tell us at info@aqlyst.ai. Describing the page, what you were trying to do, and the browser or assistive technology you were using helps us reproduce and fix it quickly.
We treat accessibility reports as defects rather than feature requests, and we will confirm receipt and tell you what we intend to do about it.