01
See clearly
Adjust text size, switch to a high-contrast colour scheme, and force always-on link underlines from the on-page accessibility menu.
Company › Accessibility
Built for
everyone.
How we make cloud.ax usable, no matter how you read, hear, move or think.
Accessibility is a feature, not a finish.
WCAG 2.2 Level AA is the floor, and we keep working past it.
This accessibility statement applies to https://cloud.ax. The site is run by Cloudax Ltd and we want as many people as possible to be able to use it. That means you should be able to:
- change colours, contrast levels and fonts using the on-page Accessibility menu or your own browser settings;
- zoom in up to 400% without the text spilling off the screen;
- navigate most of the website using just a keyboard;
- navigate most of the website using speech-recognition software;
- listen to most of the website using a screen reader (including the latest versions of NVDA, JAWS, VoiceOver and TalkBack).
We have made the website text as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability.
Four ways we try to meet you where you are.
02
Hear & be heard
Pages are screen-reader friendly with semantic landmarks, descriptive labels, and meaningful image alternatives. Forms announce errors as they happen.
03
Move with ease
Every page is fully keyboard navigable, with a 'skip to main content' link, visible focus rings, and large hit areas on interactive controls.
04
Read at your pace
Reduce motion stops animated backgrounds, readable spacing widens line height and letter spacing, and copy is written in plain English.
What works well today.
We believe these parts of the site meet WCAG 2.2 Level AA.
Resize text up to 200%
Use the on-page Accessibility menu (open it from the footer or with Alt+Shift+A) or your browser zoom; content reflows without loss of functionality.
Navigate the whole site with a keyboard
Press Tab to step through links and controls; the first keyboard stop is a 'skip to main content' link that bypasses the navigation.
Use a screen reader
We use semantic HTML landmarks (header, nav, main, footer), descriptive page titles, and ARIA labels on icon-only controls.
Respect reduced-motion preferences
If your operating system requests reduced motion, animated grainient backgrounds and transitions are paused automatically.
View in high contrast
A high-contrast theme is available from the Accessibility menu. It uses a black background, light text, and yellow headings.
Tap any control comfortably
Every link, button and tappable control on the site meets the WCAG 2.2 minimum target size of 24×24 CSS pixels, including dense areas like the footer legal links and the cookie banner.
Fill in forms with assistive tech
Every form field has a programmatically associated label, autocomplete tokens for fast password-manager and screen-reader fill-in, and inline error messages that are announced as soon as they appear (role="alert"). The first invalid field receives focus on submit, so you never have to hunt for what went wrong.
Use this site in your language
The site declares itself as British English (lang="en-GB") so screen readers pick the right pronunciation rules out of the box.
What we are still fixing.
We know parts of this website are not yet fully accessible. Here's the honest list, with our plan for each.
Animated grainient hero panels
Each main page features a slow animated colour gradient (a WebGL shader). The canvas itself is purely decorative: it is hidden when you request reduced motion or when WebGL is unavailable, and a designed multi-stop CSS gradient is shown in its place so the experience stays on-brand without animation.
Some embedded videos
A small number of news articles embed third-party videos that may not have synchronised captions or audio descriptions. We are working with our content team to caption new videos by default.
Decorative client logos
Client trust-bar logos use light brand marks against a dark hero. They are labelled with company names but their visual contrast can be below 3:1. We have given each one an accessible text alternative.
Default-palette contrast review still pending
We have completed an automated sweep of low-opacity brand utilities (text-white at 40–65 %, slate-400 body copy) and bumped them to meet WCAG 2.2 AA (4.5:1) in default mode. The remaining gap is a hand-audited, page-by-page contrast pass that covers edge cases like accent colours layered over photography or grainient hot-spots; that pass has not yet been completed.
Independent audit not yet completed
All compliance claims on this page are based on internal review, automated scans (axe-core, Lighthouse, WAVE) and the verification matrix below. We have not yet commissioned an independent third-party WCAG 2.2 AA audit. When we do, the resulting report will be linked from this page and the test matrix will be updated with the dates it covers.
Reporting accessibility problems.
We always want to hear from you: your report helps us prioritise the next fix.
We are always looking to improve the accessibility of this website. If you find any problems not listed on this page, or you think we are not meeting accessibility requirements, please contact:
- Email: [email protected]
- Phone: +44 333 011 1190
- Post:Cloudax Ltd, 167-169 Great Portland Street, London W1W 5PF
We will consider your request and aim to get back to you within 5 working days.
Alternative formats
If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille, please use the contact details above. Tell us:
- the web address (URL) of the content;
- your name and email address;
- the format you need: for example, audio CD, braille, BSL video, large print or accessible PDF.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the "accessibility regulations"). Although these regulations apply primarily to public sector bodies, we adopt the same standards voluntarily. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
How we have built the site for accessibility.
What we test, where we fall short, and what counts as a disproportionate burden.
Compliance status
This website is partially compliantwith the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Animated decorative backgroundson hero panels and call-to-action sections are intentionally decorative (aria-hidden) and pause when reduced motion is requested. We are evaluating static fallbacks for users who cannot disable motion at the OS level. This may not meet WCAG 2.2 success criterion 2.3.3 Animation from Interactions (AAA)in all states.
- Some third-party embedded videoson news and blog articles do not always include synchronised captions. We plan to caption all new content from May 2026 and retro-fit captions on the most-viewed legacy videos by the end of 2026. This fails WCAG 2.2 success criterion1.2.2 Captions (Prerecorded).
- Some legacy PDF documentsare not fully tagged for assistive technology. We plan to either replace these with accessible HTML by the end of 2026 or remove them. This fails WCAG 2.2 success criterion1.3.1 Info and Relationships and4.1.2 Name, Role, Value.
Disproportionate burden
We have not currently claimed disproportionate burden for any content on this website. If we do, we will list those exceptions here with the assessment behind them.
Content that's not within the scope of the accessibility regulations
- Third-party contentembedded from suppliers we do not control (for example calendar booking widgets, web chat, or partner videos) is not within our control. We choose vendors with strong accessibility track records and raise issues with them as soon as we find them.
- Live audioin podcasts and webinars is exempt from real-time captioning, although recordings are captioned after the event.
The processes that keep accessibility on track.
Programmatic checks at every release
Every front-end release runs an automated WCAG audit (axe-core) in CI; pull requests that introduce new accessibility regressions cannot be merged. Keyboard-only navigation and 200 % zoom are part of the manual smoke check before each deploy.
Assistive-technology testing
End-to-end screen-reader passes against NVDA, VoiceOver, JAWS and TalkBack are not yet completed. The matrix further down this page lists exactly which flows are still pending and is updated with the real test date the moment a flow has been walked through with a real assistive technology. We will not pre-fill claims we have not actually verified.
Continuously improved
We treat accessibility as ongoing work, not a tick-box. This statement is reviewed at least annually, and any time we make a substantial change to the site.
What we have verified, where, and with what.
A transparent log of how each accessibility claim on this page was checked. We separate things that can be confirmed by code review from things that genuinely require a human and an assistive technology, and we are honest about which assistive-tech tests have not yet been carried out.
Programmatic verification
The following items are confirmed via code review, our component library, automated scans (axe-core, Lighthouse, WAVE) and the dev-tools accessibility tree. They are stable across releases because they are baked into the shared components every page uses.
| Check | Where | Status | Last verified |
|---|---|---|---|
lang="en-GB"on<html> | client/index.html | Pass | 3 May 2026 |
Viewport allows pinch-zoom (nomaximum-scale oruser-scalable=no), WCAG 1.4.4 / 1.4.10 | client/index.html | Pass | 3 May 2026 |
| Skip-to-content link | All pages (first focusable element) | Pass | 3 May 2026 |
Single<main id="main-content">landmark per page | Home, PageHero, PolicyShell, 404 | Pass | 3 May 2026 |
Form labels associated viahtmlFor/id | Contact form, Demo form (all steps) | Pass | 3 May 2026 |
Errors announced (role="alert") and linked viaaria-describedby | Contact form, Demo form | Pass | 3 May 2026 |
Required fields marked with botharia-required and a screen-reader-only "required" hint | Contact form, Demo form | Pass | 3 May 2026 |
First invalid field receives focus on submit (react-hook-formshouldFocusError) | Contact form, Demo form | Pass | 3 May 2026 |
Toast feedback inside anaria-liveregion | Site-wide (Radix Toast) | Pass | 3 May 2026 |
Cookie banner usesrole="region"+ aria-labelledby, not a focus-trapping dialog | Cookie consent component | Pass | 3 May 2026 |
All<img>have explicit alt; decorative avatars use empty alt=""+aria-hidden | Footer, Navbar, Testimonials, Team, Case studies | Pass | 3 May 2026 |
| Touch targets ≥ 24×24 px (WCAG 2.5.8) | Footer legal & site nav, social icons, cookie banner, mobile log-in | Pass | 3 May 2026 |
| Reduced-motion: WebGL canvas hidden, designed static gradient shown | All hero panels (PageHero) | Pass | 3 May 2026 |
Low-opacity brand utilities removed from body copy (text-white/40–65,slate-400) | Site-wide automated sweep | Pass | 3 May 2026 |
| Page-by-page hand contrast audit (default mode) | All public pages | Not yet completed | — |
Assistive-technology testing
The matrix below lists the flows we plan to walk through with a real screen reader on a real machine. We will only ever mark a row "Pass" once a person has actually used the page with that assistive tech end-to-end and confirmed the announcements match the design intent. Until then, every row stays as Not yet tested.
We deliberately do not commit to a date here: promising a "scheduled audit" before one is genuinely booked would be dishonest. When a flow is actually tested, this page is updated with the real date, the OS / browser / AT version used, and any announcement quirks fixed as a result.
| Flow | OS | Browser | Assistive tech | Status | Date |
|---|---|---|---|---|---|
| Home → Solutions → Contact us | Windows 11 | Firefox (latest) | NVDA 2024.x | Not yet tested | — |
| Contact form (submit + validation errors) | Windows 11 | Chrome (latest) | NVDA 2024.x | Not yet tested | — |
| Try-demo form (3-step wizard, validation, success state) | macOS 14 | Safari 17 | VoiceOver | Not yet tested | — |
| Cookie banner accept / reject from keyboard | macOS 14 | Safari 17 | VoiceOver | Not yet tested | — |
| Accessibility widget (open, toggle, persist, reset) | Windows 11 | Edge (latest) | JAWS 2024 | Not yet tested | — |
| Mobile navigation (open, expand, collapse, item activate) | iOS 17 | Safari Mobile | VoiceOver | Not yet tested | — |
| Mobile navigation (Android) | Android 14 | Chrome Mobile | TalkBack | Not yet tested | — |
If you use assistive technology and run into something that does not announce correctly, please tell us; we treat AT bug reports as higher priority than feature work.
How and when this statement was made.
This statement was prepared on3 May 2026. It was last reviewed on3 May 2026.
The website was last audited against WCAG 2.2 AA in April 2026. The audit combined automated scans (axe-core, Lighthouse, WAVE) with manual keyboard and screen-reader testing across the home, solutions, company and policy pages.
The audit was carried out internally by the Cloudax engineering and design teams. We sampled the highest-traffic pages plus a representative spread of templated pages to make sure repeating components (navigation, footer, forms, hero panels) were assessed.
Tools you can use right now
Our on-pageAccessibility menulets you immediately:
- resize text to large or extra-large;
- switch on a high-contrast theme;
- pause animated backgrounds (reduce motion);
- force underlines on all links;
- show a stronger keyboard focus ring;
- increase line height and letter spacing for easier reading.
Open the Accessibility menu now
You can also reach it from the footer of any page, or by pressingAlt+Shift+A.
Your choices are stored on your device only and apply across the whole site.
We follow your device settings
On your first visit, we automatically pick up the accessibility preferences you have already set in your operating system or browser, so you do not have to re-toggle anything here. Specifically:
- Reduce motion: if your device requests it (the
prefers-reduced-motionmedia query), animated backgrounds and transitions are paused throughout the site. - Higher contrast: if your device requests it (the
prefers-contrast: moremedia query) or you are using Windows High Contrast Mode (forced-colors: active), our high-contrast theme is enabled by default.
If you prefer a different combination, your manual choices in the on-page Accessibility menu always win over the OS defaults.
Tell us when we get it wrong.
If part of this site is hard to use because of how it is built (not because of what it says), please tell us, even if it is not listed above.
Cloudax Ltd is registered in England & Wales, Company No. 14717183.
Last updated: 3rd May 2026
Report an accessibility problem.
We aim to reply within 5 working days. You can also call us on +44 333 011 1190.
For all other enquiries, see our contact page.
See how Cloudax's more human AI can transform your business
No commitment, free consultation included
Let's Talk