Accessibility Statement

Our commitment, our current status, and how to report a barrier.

Last updated 8 August 2026

Our commitment

Aurea aims to meet WCAG 2.2 level AA across both the application and every website it generates. Accessibility is treated as a correctness requirement, not a feature.

What this means in practice

Semantic HTML with proper landmarks and heading order, full keyboard operability, visible focus indicators on every interactive element, colour contrast above 4.5:1 for body text and 3:1 for large text and interface components, text alternatives for meaningful images, form labels bound to their controls, and complete respect for the operating system's reduced-motion preference.

Generated websites

Accessibility is built into the templates, so the sites Aurea produces inherit all of the above automatically. This applies on the Free plan — it is not a paid upgrade.

Known limitations

Complex data visualisations in the analytics dashboard currently provide summary text rather than a full accessible table. We are addressing this.

Reporting a barrier

If any part of Aurea is difficult or impossible to use, please tell us. We treat accessibility reports as bugs and prioritise them accordingly. You will get a response within one working day.

Questions about this document?

Write to us and a person will answer — we do not route legal or privacy questions to a form that goes nowhere.