Accessibility
Our accessibility statement, written honestly
We build to WCAG 2.2 Level AA and we sell accessibility remediation as a service, which means this site has to stand up to the standard we hold clients to. Below is what we have actually done, what we know is still short, and how to tell us when something does not work.
The standard we work to
WCAG 2.2, Level AA, as a build constraint
The Web Content Accessibility Guidelines 2.2, Level AA, are the benchmark we design and build against — for this site and for client work. They are also the standard most commonly referenced when accessibility is raised as a legal question in the United States.
Accessibility is part of the build on every project, not a line item that can be removed to hit a budget. Semantic structure, focus visibility, contrast and reduced-motion support cost almost nothing when they are done during the build, and a great deal when they are retrofitted.
That said, "we follow WCAG" means very little on its own. The specifics below are what the claim is actually made of.
What we have built in
Specifics, not reassurances
Each of these is checkable. Tab through the site, turn on reduced motion in your operating system, or read the source — that is rather the point of listing them.
Semantic HTML, not div soup
Navigation is a <nav> with a list, the breadcrumb trail is an ordered list with aria-current on the current page, quotes are <figure> and <blockquote>, statistics are a definition list, and the FAQ accordions are native <details>/<summary>. Anything that acts like a button is a <button>; anything that navigates is a link.
Visible focus on everything interactive
A 2px brand-coloured focus ring with a 3px offset is applied globally through :focus-visible. We have not suppressed default focus styling anywhere on the site.
A skip link to the main content
The first focusable element on every page jumps past the header to the main landmark.
prefers-reduced-motion is honoured globally
The drifting gradient fields, floating cards, marquees and count-up numbers all stop when the operating system requests reduced motion. The count-up renders its final value in the server HTML, so the number is correct before any JavaScript runs — and with JavaScript disabled entirely.
Contrast chosen against the AA thresholds
Body and heading colours were selected to clear 4.5:1 on white. Two brand colours were deliberately replaced during the rebuild: the brighter brand blue reaches only about 4.0:1 behind white text, so the darker blue carries every button, link and text use, and the standard WhatsApp green was darkened because white on it falls below even the 3:1 non-text threshold. The lighter brand tones are used for graphics and backgrounds only.
A keyboard-operable mega menu
The Services and Industries panels open when their trigger receives keyboard focus, close on Escape, and every item inside is a real link reached by tabbing in document order. No part of the navigation requires a mouse or a hover.
No carousels that trap you
The testimonial rail is CSS scroll-snap over real links and figures, not a JavaScript slider. Tabbing moves through the cards and the rail follows. Nothing auto-advances while you are reading it.
Text that resizes and reflows
Layouts are built in relative units and tested from 320px, so the site reflows without horizontal scrolling and text can be enlarged without content being clipped.
Images carry real alternative text
Meaningful images have descriptive alt text. Decorative gradient fields and icons are marked aria-hidden so screen readers skip them instead of announcing noise.
Known limitations
Where this site is still short
A statement that lists no limitations has not been written carefully. These are the gaps we are aware of today; the list changes as things are fixed and as new issues are found.
- This site has not yet been independently audited. Everything above is our own assessment, and we would rather say so than imply a certification we do not hold.
- We have not completed a full assistive-technology test matrix. Testing to date has been manual keyboard and automated tooling, not a structured pass across NVDA, JAWS and VoiceOver.
- The mega menu is a disclosure pattern rather than a full ARIA menu widget. It is operable by keyboard, but it does not implement arrow-key traversal or focus cycling within the panel.
- The horizontal testimonial rail has no explicit previous and next buttons. Keyboard and screen-reader users reach every card by tabbing, but there is no discrete paging control.
- Older case-study assets and any PDFs carried over from the previous site may not be tagged or structured to the same standard as pages built in this rebuild.
- Third-party embeds — maps, and any video or booking widget added later — are outside our direct control, and their accessibility is set by their vendors.
- Colour contrast is verified against WCAG 2.2 AA for body and interface text. The brand blue at its lightest is used for large display text and non-text elements only, where the 3:1 threshold applies rather than 4.5:1 — a deliberate choice, but one worth knowing about.
Tell us
If something here does not work for you, we want to know
You do not need to know what the problem is called, and you do not need to be polite about it. Tell us what you were trying to do and what happened.
If you can, include:
- The address of the page.
- What you were trying to do when it went wrong.
- The browser, device and any assistive technology you were using — for example Chrome on Windows with NVDA, or Safari on iPhone with VoiceOver.
We acknowledge every accessibility report within one working day and tell you what we intend to do about it, including when we are not able to fix something quickly and why.
If you need information from this site in another format — large print, plain text, or read out over the phone — ask and we will provide it.
If you have raised something with us and are not satisfied with the response, reply to the same thread and ask for it to be escalated — it goes to the studio owner, who will answer within five working days with either a fix, a date for one, or a straight explanation of why we are not going to do it. Beyond that, complaints about the accessibility of a US business can be filed with the Civil Rights Division of the Department of Justice at civilrights.justice.gov. We would much rather hear from you first.
We do this for clients too
Accessibility work on your site
Audit against WCAG 2.2 AA, a prioritised remediation plan, and the fixes themselves — on a site we built or one we did not. If you have had a demand letter, start with the audit.