Accessibility statement

We build software for a living, so an inaccessible website of our own would be a poor advertisement. This page says what we aim for, how we check it, and where we know we fall short.

Last reviewed: 6 August 2026

Our commitment

Cloudadorn aims to make cloudadorn.com usable by everyone, including people who navigate by keyboard, use a screen reader or magnifier, need high contrast or reduced motion, or are simply on a small screen with one hand.

Conformance status

Target: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

Status: partially conformant, self-assessed. “Partially conformant” means most of the site meets the target and some parts may not. “Self-assessed” means this claim comes from our own automated and manual testing, not from an independent audit. We have not commissioned a third-party accessibility audit, and we would rather say so than let the word “compliant” imply one.

What we have built in

  • A skip link to main content on every page, and a single <h1> per page with a heading order that does not skip levels.
  • A visible focus indicator on every interactive element, designed to stay visible on both the light and dark surfaces of the site.
  • Full keyboard operation: the mobile menu can be opened, navigated and closed with a keyboard, closes on Esc, keeps focus inside while open, and returns focus to the control that opened it. Academy masterclasses are ordinary pages, so they inherit the same keyboard and focus behaviour as the rest of the site.
  • Text contrast of at least 4.5:1 against the surface it sits on, verified per surface rather than assumed.
  • Meaningful alternative text on diagrams; decorative images marked as decorative so a screen reader skips them rather than reading a filename.
  • Form fields with real labels, errors tied to their field programmatically, and focus moved to the first field that needs attention.
  • prefers-reduced-motion honoured — all animation and smooth scrolling is decorative here, so it is switched off entirely rather than shortened.
  • Support for Windows high contrast / forced-colors mode, including the gradient labels that would otherwise disappear.
  • Nothing conveyed by colour alone, and no horizontal scrolling from 320px upward.
  • A print stylesheet, so a page can be read on paper without the navigation furniture.

How we test

  • Automated checks with axe-core across every page and both mobile and desktop widths, run as part of our build verification rather than occasionally by hand.
  • Manual keyboard-only traversal of each page, including the menu, Academy articles and the contact form.
  • Rendering checks in Chromium, Firefox and WebKit at 390, 768, 1280, 1440 and 1920 pixels wide.
  • Colour contrast computed against the actual background of each element.

Known limitations

Being specific here is more useful than a blanket assurance:

  • No independent audit. Everything above is self-assessed. An external audit would very likely find issues we have not.
  • Limited screen-reader coverage. Our manual testing has focused on structure, focus order and announcements rather than exhaustive testing across every screen reader and browser pairing. Behaviour in a combination we have not tried may differ.
  • Diagrams are complex images. Each carries alternative text and sits beside a written explanation that covers the same ground. For some readers the prose will be the more useful of the two, and that is intended.
  • Third-party form delivery. Submitting the contact form hands off to an external delivery service. We control our form; we do not control that service's own pages if you ever land on one.
  • No published VPAT. If your procurement process needs an Accessibility Conformance Report, ask us and we will tell you honestly what we can and cannot supply.

Tell us about a barrier

If something on this site blocked you, we want to know — a specific report is worth more than any statement on this page.

Email info@cloudadorn.com with “accessibility” in the subject, or call +1 (678) 208 5818 during office hours. It helps if you can tell us the page, what you were trying to do, and what you are using — but report it even if you cannot.

We aim to acknowledge within five business days and to tell you what we are going to do about it, including if the answer is that we cannot fix it quickly.

If you need information from this site in another format so that you can act on it, ask and we will send it.

This statement covers cloudadorn.com only. Accessibility requirements for software we build for you are an engagement matter — and one worth raising early rather than at acceptance testing.

Raise it with us