Virtual 3 Sixty Request a quote

Accessibility

Accessibility statement

We want this site to work for everyone who visits it. Here is what we have done, where the gaps are, and how to tell us when we have got something wrong.

What we aim for

This site is built to meet WCAG 2.1 Level AA. In practice that means every page has a skip link and proper landmarks, one h1 and a sensible heading order, visible focus outlines on everything you can reach with a keyboard, text that meets AA contrast against its background, real alternative text on meaningful images and empty alt on decorative ones, form fields with real labels, and no reliance on color alone to convey meaning.

Animation is a preference, not a requirement. If your device is set to reduce motion, the rotating panorama on the home page stops and the scroll animations do not run. Nothing on the site depends on motion to be usable.

The accessibility toolbar

The button at the bottom left of every page opens a toolbar with text sizing up to 175%, line height and letter spacing controls, a readable font, several contrast modes, link highlighting, stronger focus rings, a large cursor, a reading guide and an option to stop animations. Your choices are remembered in your browser.

We want to be straight with you about what that toolbar is. It is a convenience layer, not a compliance certificate. Overlay widgets do not make a website accessible, and we would not want anyone to believe otherwise. What actually makes this site usable is the markup underneath: the landmarks, the headings, the labels, the contrast and the keyboard order. The toolbar sits on top of that as a genuine convenience for people who want it.

Known limits

Two things on this site are honestly outside our full control:

  • The panorama viewer. The 360° tours use a third-party panoramic viewer. It is operable with a keyboard, but the experience of a spherical photograph is inherently visual and we cannot make it equivalent for a screen-reader user. Where a tour matters to you and you cannot use it, call us and we will describe the space or send you stills.
  • Embedded Google content. Maps and Street View embeds are Google’s markup, not ours, and their accessibility is theirs to determine. We load them only when you ask for them so they never get in your way unprompted.

How this was tested

Pages are checked against the automated axe accessibility rules, validated as HTML and CSS through the W3C validators, and reviewed by keyboard. Automated testing catches perhaps a third of real accessibility problems, so if you hit something a machine missed, we would genuinely like to hear about it.

Tell us

If any part of this site does not work for you, contact us and we will fix it or find another way to get you what you need.

We aim to respond within two business days. If a fix will take longer than that, we will tell you what we are doing and when to expect it.