Accessibility

Our commitment

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. blury is built and run by a single operator and has not been independently audited, so we do not claim full conformance. Parts of the product almost certainly fall short of that standard today. We treat accessibility problems as bugs and fix them like bugs.

Known limitations

We have not completed a formal audit, so we cannot publish a full list. Areas we consider most likely to have gaps:

• The writing editor and its formatting toolbar, which rely on rich text editing behaviour that is difficult to expose well to assistive technology.
• Streaming responses, where text appears progressively and may not be announced in a useful order.
• Colour contrast in secondary and placeholder text.

If you hit something not listed here, that is useful information and we would like to hear it.

Requesting an accommodation or reporting a barrier

Email hello@blury.ai with the subject line “Accessibility”. Tell us what you were trying to do, what got in the way, and what assistive technology you use if that is relevant. There is no form to fill in and no account required.

We aim to acknowledge accessibility messages within five business days and to tell you either how to work around the problem, when we expect to fix it, or that we cannot fix it and why. If a feature is unusable for you and we cannot fix it promptly, tell us and we will arrange a refund or another reasonable alternative.

Feedback in another format

If email does not work for you, say so and we will arrange another way to communicate. We can provide the content of this page, our Terms of Service, and our Privacy Policy in an accessible format on request, at no charge.

Scope

This statement covers blury.ai and its subdomains. It does not cover third-party services we rely on, such as our payment processor’s hosted checkout pages, which are governed by their own accessibility practices.