This statement covers the Verand marketing site at verand.ai and the signed-in Verand application at app.verand.ai. They’re different surfaces with different problems. The marketing site is largely static pages of text. The application is a data-dense dashboard carrying tables, charts, a document editor and live run status. We hold both to the same standard, and where one is further along than the other we’ll say so here rather than average the two into a single claim.
Third-party components we embed, and the websites our customers publish to, sit outside this statement. We can’t speak for code we don’t control.
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium. It’s the bar we’re building against on both surfaces, and the link goes to the specification itself rather than to a summary of it.
We’re naming it so you know which reference to hold us to, and so a barrier you report to us has a shared vocabulary behind it. Naming a target is not the same as meeting it. The next section says where the work actually stands.
This is a commitment and an ongoing effort. It isn’t a certified result, and we’re not claiming conformance.
To be specific about what has not happened:
- no independent accessibility audit of the marketing site or the application has been carried out;
- we hold no third-party assessment, no VPAT and no accessibility conformance report;
- we’re not publishing a list of success criteria as met, because we haven’t tested against them.
Accessibility work happens inside our normal development rather than as a separate audited programme, so the honest position is that we’ve built with the standard in mind and have not measured the result against it. We’d rather write that down than publish a conformance claim we can’t support.
If you’re evaluating Verand against accessibility obligations of your own, read this page as a statement of intent and a working channel, not as evidence of a conformance level. Ask us directly about anything specific you need to establish and we’ll tell you what we know and what we don’t.
If any part of verand.ai or the Verand application stops you doing something, tell us. Email support@verand.ai. Reports are welcome, and a specific one is the most useful kind. Where you can, include:
- the page or screen, with the URL if you have it;
- what you were trying to do;
- what happened instead;
- your browser and operating system, plus any assistive technology and its version.
If none of that is to hand, send the report anyway. One line describing what you couldn’t do is worth more to us than a report you didn’t send.
We’ll acknowledge every report, tell you what we found, and say what we’re going to do about it. Where a fix isn’t quick we’ll say that too, and give you whatever route exists to get the same thing done in the meantime.
We haven’t set a formal response time, so we’re not going to quote one. What we can say is that a barrier report is treated as a defect, not as feedback, and it goes to a person rather than a queue.
Accessibility reports don’t go through a separate process. They reach the same inbox our support requests reach, and they’re handled as defects rather than as feedback.
If something here isn’t usable for you, we can get you the same content another way. Email support@verand.ai and say what works: plain text, a larger-print version, a file you can run through your own tools, or a person who’ll walk you through it.
That applies to anything on this site, the pricing, terms and privacy policy included. Ask for what you need.