Velo
Sign inStart a review

Accessibility

Accessibility is part of the review.

Velo's accessibility target is that creating, reading, and responding to feedback does not depend on a pointer or animation. This page states the commitments guiding testing and refinement.

Try it

The commitments, on this page, in the real components.

Tab through these. The ring appears for the keyboard and stays out of the way of a pointer.
  • Text on the pageLight 15.4:1, AAADark 13.7:1, AAA
  • Secondary text on a panelLight 5.2:1, AADark 7.1:1, AAA
  • The primary actionLight 15.4:1, AAADark 13.7:1, AAA
The pairs this page sets, measured from the colour tokens in both themes.
Play the reveal

A note rises into place and settles.

With Reduce Motion on, the line is simply there: no rise, no fade.

Four commitments

  1. Keyboard and focus

    Our keyboard target is that every core review action can be reached without a pointer. We commit to testing visible focus and logical tab order across capture, upload, pin, share, and comment flows.

    Dialogs and dismissible surfaces are part of that target: keyboard users should have a clear way to close them and return to the work.

  2. Screen readers and structure

    Our screen-reader target is for semantic headings, landmarks, labels, and status messages to provide a readable map of the page. The release, pins, threads, and access controls should be encountered in a meaningful order.

    Feedback should remain understandable without relying on a visual position alone; its text and relationship to the reviewed work need a clear name.

  3. Contrast and motion

    Our contrast target is for text, controls, and focus indicators to remain legible against their surfaces. Status should not be communicated by color alone.

    Our reduced-motion target is to remove or shorten transitions when someone requests reduced motion, so no important interaction should depend on movement.

  4. Contact us when something gets in the way

    If a page or review flow is difficult to use, email Accessibility feedback. Tell us the page, browser or device, what you expected, and what would make the task possible.

    We use that detail to prioritize fixes and improve the next review. You can also read the privacy policy to understand how a support message is handled.

Evidence limit: these are product targets and testing commitments. This page does not establish that every flow currently meets them.