Skip to content
Policy centre
ACCESSIBILITY STATEMENT

Access should be part of the design.

How Leadvera is built to be accessible, its known limits and how to tell us about a problem.

Effective 8 November 20263 min read
Provider
Leadvera Ltd (trading as Leadvera)
Accessibility contact
support@unisticgroup.com

1. Our design approach

The interface is designed to support clear reading, keyboard operation, visible focus, labelled forms, flexible layouts and reduced-motion preferences. These are implementation choices, not a claim of certified conformance.

Leadvera has not yet had an independent accessibility audit. A full assessment will cover the whole experience, including sign-in, connected integrations and generated content.

2. Features included

Leadvera includes the following accessibility features. We also test with people and assistive technology as the product changes.

  • Semantic headings, labels and clear link text.
  • Visible keyboard focus and native form controls.
  • Escape and focus management for implemented dialogs.
  • Responsive layouts with scrollable data regions.
  • Reduced-motion rules for non-essential animation.
  • Text explanations alongside icons and status indicators.

3. Known limits

Some dense data tables and pipeline boards require horizontal scrolling on smaller screens. File content supplied by users and external connected services will need their own accessibility checks.

A complete audit against an agreed accessibility standard has not been completed. Screen-reader combinations, keyboard-only end-to-end journeys, contrast, zoom and error recovery are part of that assessment.

4. Tell us where a journey breaks

Helpful feedback identifies the page, task, issue and any browser or assistive technology involved. Avoid including customer records, passwords or medical details. You can also write to support@unisticgroup.com.

The feedback form below sends your report to the Leadvera team with a reference number. Add your email if you would like a reply.

5. Review and improvements

We prioritise issues that block access to a core task, check each fix with the affected interaction, and review new features before release.

This statement was last reviewed on 8 November 2026.