Accessibility statement

The standard we are working to

The target is WCAG 2.2 Level AA. That is also the standard the European Accessibility Act has required of consumer-facing services since 28 June 2025.

What has been tested

Every page listed below was audited with axe-core against a production build, using the combined wcag2a, wcag2aa, wcag21a, wcag21aa and wcag22aa rule sets. All nine pages currently return zero violations:

• Home, Tower, Experience, Residence
• Floor plan, Gallery, Contact
• Privacy, Terms

Alongside that, the following hold by construction and were checked by hand in the source: colour pairs are chosen against a measured contrast ratio rather than by eye; motion — parallax, camera drift and the scroll-driven reveals — is disabled when the operating system reports prefers-reduced-motion; and the 3D views fall back to a described notice rather than a blank rectangle when WebGL is unavailable.

What has not been tested

Automated tools detect only a portion of the WCAG success criteria — roughly a third, on the most generous published estimates. A clean axe run is therefore a floor, not a certificate. Specifically, none of the following has been carried out:

• Manual testing with a screen reader (NVDA, JAWS or VoiceOver).
• Testing with speech input, screen magnification or a switch device.
• Testing with people who have disabilities.
• An independent third-party audit.

Until those are done, this site should be described as substantially conforming on automated criteria, and not as fully WCAG 2.2 AA conformant.

Known limitations

• The walkthrough is not operable by screen reader. Walk mode can now be driven three ways — the movement keys, with Q, E, R and F to turn and look; a mouse; or two thumb sticks on a touch screen — so it no longer requires a pointer and no longer excludes phones and tablets. What it still cannot do is describe itself: a visitor using a screen reader is told the frame’s subject and nothing about what is in it.
• The thumb sticks are pointer-only. They mirror controls that already exist on the keyboard, so they are hidden from assistive technology rather than exposed as two unlabelled drag targets a screen reader could not operate.
• The 3D views are announced, not transcribed. Each rendered frame carries a text label describing the view, but the scene itself is not navigable by assistive technology. The floor plan page presents the same layout as structured, labelled drawings, and is the accessible route to that information.
• The walkthrough is demanding on hardware. Quality is reduced automatically on weaker devices, but on older hardware the experience may still be slow.

Feedback

This section is not yet complete. An accessibility statement must give a monitored contact route for reporting barriers, and no contact address has been configured for this deployment. Before this site is published, the operator must set one and name it here, together with the response time they undertake to meet. Until then the enquiry form is the only route available.