Accessibility Statement
This statement was prepared in July 2026
In short: this website aims to conform to WCAG 2.2 Level AA and EN 301 549 — the same standard we recommend to every marketing client, since websites and landing pages selling to EU consumers now fall under the European Accessibility Act. This page sets out what we've done, what we know still falls short, and how to report an accessibility problem — we aim to respond and start fixing genuine issues within one business day.
1. Our commitment
Ripple18 is committed to making ripple18.co.uk usable by as many people as possible, including people using assistive technology such as screen readers, screen magnification, speech input or keyboard-only navigation. Accessibility isn't a compliance checkbox for us — as of 28 June 2025 the European Accessibility Act is legally enforceable across the EU, meaning inaccessible landing pages and campaign sites are now a genuine business and legal risk for the brands we run marketing for, so we hold our own site to the standard we advise on.
2. Conformance status
This website aims to conform to WCAG (Web Content Accessibility Guidelines) 2.2, Level AA, and to the harmonised European standard EN 301 549, which WCAG 2.2 AA satisfies for web content.
A note on scope: the European Accessibility Act (EAA) applies in full to specific product and service categories — e-commerce, banking, e-books and similar — and this marketing-agency website, as a B2B services site, may fall outside that strict legal scope. Rather than relying on that distinction, we apply the WCAG 2.2 AA / EN 301 549 standard to our own site voluntarily, as the baseline we build every campaign landing page to.
We describe our conformance as partially conformant: we believe most of the site meets the standard, checked with automated tooling and manual testing, but we have not commissioned an independent third-party audit, and the known limitations in section 4 below have not yet been resolved.
3. What we've done
- A "skip to main content" link at the top of every page for keyboard and screen-reader users.
- Semantic HTML landmarks and heading structure, with exactly one <h1> per page.
- A visible focus indicator on every interactive element (keyboard focus is never hidden).
- Full keyboard operability for interactive components — including the FAQ accordions used on our FAQs page, which expose
aria-expanded,aria-controlsandrole="region"to assistive technology. - Accessible form validation — error messages are associated with their field via
aria-describedby, announced withrole="alert", and on success, focus is moved to the confirmation message so keyboard/screen-reader users aren't stranded. - Colour choices checked for WCAG AA contrast between text and background.
- Motion that respects your system's
prefers-reduced-motionsetting — page transitions and scroll animations are removed entirely for visitors who've asked for reduced motion, not just shortened. - A responsive layout that supports browser text resizing and zoom without loss of content or function.
- Descriptive alt text on meaningful images; decorative graphics are hidden from assistive technology.
- Regular manual testing with a keyboard and with screen readers, alongside automated accessibility tooling.
4. Known limitations
We are not aware of any content on this site that is fully inaccessible, but we know accessibility work is never fully "done." Areas we're continuing to monitor and improve:
- We have not yet commissioned an independent third-party WCAG audit — our own conformance checks are automated tooling plus manual keyboard/screen-reader testing by our team, not an external assessor.
- As the site grows (new pages, new components), each addition is checked against WCAG 2.2 AA before launch, but we treat this as an ongoing process rather than a one-off certification.
If you encounter a barrier not listed here, please tell us — see section 6.
5. Technical specification
This website relies on HTML, CSS and JavaScript. Core content and navigation are readable and usable without JavaScript; JavaScript is used progressively, for enhancements such as the FAQ accordion and scroll-reveal animation, neither of which is required to read or navigate the site.
6. Reporting an accessibility problem
If you have trouble accessing any part of this site, we want to know. Please tell us:
- The page URL where you had a problem
- What you were trying to do
- Your browser, device or assistive technology, if relevant
Contact us by email at hello@ripple18.co.uk, or use our contact form — both are accessible without needing to navigate the barrier you're reporting. We aim to acknowledge accessibility reports within one business day, the same response time we commit to for every enquiry, and to prioritise genuine accessibility barriers ahead of routine work.
7. Date of this statement
This statement was prepared in July 2026 and will be reviewed at least annually, and whenever a significant change is made to the site.