1. Conformance status
Our target is WCAG 2.2 (Web Content Accessibility Guidelines, version 2.2), Level AA — the current, internationally recognised standard for web accessibility, and the level referenced by EN 301 549 and most enterprise accessibility procurement requirements.
We are working towards full conformance with WCAG 2.2 Level AA. The measures below have been built into the site and checked directly; a complete audit of the finished site against the full standard is planned before we describe the site as fully conformant.
2. Measures we’ve taken
- Automated and manual testing. We test pages against the WCAG 2.1/2.2 AA ruleset using axe-core, run in a real browser rather than a static tool, and follow up any flagged issue by hand rather than taking automated results at face value.
- Colour contrast. Every text and background colour pairing in our design system is calculated against the WCAG AA contrast thresholds (4.5:1 for normal text, 3:1 for large text and for interface components like button borders and focus indicators) before it’s used, not chosen by eye.
- Keyboard access. Every interactive element on the site — links, buttons, menus, form fields — can be reached and used with a keyboard alone, with a visible focus indicator at each stop.
- Touch and pointer. Every clickable target meets a minimum 44×44 pixel size, and nothing on the site depends on a mouse-only “hover” to reveal information or controls that a touch-screen or keyboard user would otherwise miss.
- Reduced motion. If your device is set to reduce motion, our animations (including the homepage hero and image carousels) respect that setting rather than overriding it.
- Screen readers. Menus, expandable sections and embedded video carry the correct underlying markup (ARIA attributes and accessible names) so screen-reading software announces their state correctly, and images carry descriptive alt text.
3. Contrast in practice: our buttons and call-to-action states
As a concrete example of how the above is applied, here is the actual contrast ratio behind every state of our primary and secondary call-to-action buttons, calculated against our real brand colours rather than shown as an illustration:
| Button / state | Text colour on background | Contrast ratio | WCAG AA requirement | Result |
|---|---|---|---|---|
| Primary CTA — default | Ink on Coral | 6.4:1 | 4.5:1 (normal text) | Pass |
| Primary CTA — hover | Ink on Coral (hover shade) | 5.0:1 | 4.5:1 | Pass |
| Primary CTA — pressed/active | Ink on Coral (active shade) | 4.7:1 | 4.5:1 | Pass |
| Secondary CTA — default | White on Violet | 4.6:1 | 4.5:1 | Pass |
| Secondary CTA — hover | White on Violet (hover shade) | 5.9:1 | 4.5:1 | Pass |
| Secondary CTA — pressed/active | White on Violet (active shade) | 7.1:1 | 4.5:1 | Pass |
| Tertiary (outline) CTA — default | Ink on white, outlined | 17.9:1 | 4.5:1 | Pass |
| Keyboard focus ring — on light backgrounds | Violet ring on white | 4.6:1 | 3:1 (non-text/UI components) | Pass |
| Keyboard focus ring — on dark backgrounds | Amber ring on Midnight | 11.4:1 | 3:1 (non-text/UI components) | Pass |
Disabled buttons are dimmed and cannot be interacted with (pointer-events: none); WCAG does not set a contrast requirement for inactive controls, so this state is exempt rather than a gap.
4. Known limitations
We are not aware of any parts of the site that fall short of WCAG 2.2 AA at the time of writing. If you find something that doesn’t work for you, please tell us — see below.
5. Tell us about an accessibility problem
If you have difficulty accessing any part of this website, please email us at enquiries@saascada.com and let us know the page and the problem you encountered. We aim to respond within a reasonable time and will do our best to provide the information or service you need in a way that works for you.
6. About this statement
This statement was prepared on 5 August 2026 and will be reviewed periodically as the site changes.
SaaScada Ltd is registered in England and Wales, company number 09146473.