Accessibility statement
Last updated:
VeloWise aims to be usable by everyone, including people who use a keyboard, a screen reader, magnification or reduced motion.
Our target
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the public pages and the analysis workspace. We have not had an independent accessibility audit, so we do not claim full conformance.
What we have done
- Every control can be reached and used with a keyboard, and scrollable tables become focusable when they overflow.
- A “Skip to content” link is the first thing on every page.
- Focus is always visible with a clear focus style.
- Charts have text alternatives, and the figures behind them are available as data tables.
- Animations are turned off when your system asks for reduced motion.
- Sign-in is passwordless, so there is no password to remember or type.
- Automated accessibility tests (axe) run against pages as part of our test suite.
Known limitations
- Automated tests find only some kinds of problems. Pages have not been reviewed with every combination of screen reader and browser.
- Some dense charts are easier to read in their data table than in the chart.
- Third-party content we do not control, such as Google ads on public pages, Stripe checkout and Atlassian’s sign-in screens, follows those providers’ own accessibility practices.
- Data you import is shown as it appears in your source. Issue summaries and other text written by your team may not be in plain language.
Report a problem
If something is hard or impossible to use, contact the operator of this deployment. Tell us the page address, what you were trying to do, and the browser and assistive technology you use. We will reply and, where we can, offer the information in another way while we fix it.
Related: privacy, methodology.