Unified.to

AccessibilityatUnified.to

Last updated: 26 August 2026

Unified.to is committed to making our products usable by everyone, including people who rely on assistive technologies. We treat accessibility as an ongoing part of how we build and maintain our web application, not a one-time project. This statement explains the standard we hold ourselves to, where we stand against it today, how we test, and how to reach us if something isn't working for you.

Scope

This statement covers the Unified.to web application at app.unified.to — the dashboard used to configure integrations, manage connections, view logs and webhooks, and administer a workspace.

It does not cover:

  • Third-party content displayed inside the application (for example, an integration provider's own authorization screens).
  • Our API, SDKs, and developer documentation at docs.unified.to, which are covered under separate, ongoing review.
  • Marketing pages on unified.to, which are reviewed on their own cadence.
Conformance status

We measure ourselves against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, which also encompasses WCAG 2.1 Level AA.

In August 2026 we commissioned an independent accessibility audit of app.unified.to (Accessibility Conformance Report, VPAT® 2.5Rev International, dated 20 August 2026) covering twelve representative views: Dashboard, Integrations, Embedded Components, API Keys, Settings, Connections, Webhooks, Logs, Event Notifications, Help, Support Tickets, and API Explorer. We have since remediated the issues that audit identified across six areas of work (see What we've done below).

Current status: partially conformant with WCAG 2.2 Level AA, with substantial conformance across the application shell and primary workflows. "Partially conformant" means most of the application meets the standard, and we are actively resolving the remaining gaps described under Known limitations. We will update this statement as our conformance improves and as we re-audit.

The application has also been aligned with the corresponding requirements of:

  • Section 508 of the U.S. Rehabilitation Act (which references WCAG 2.0 Level AA).
  • EN 301 549 (the European accessibility standard for ICT procurement).
What we've done

Our August 2026 remediation addressed the audit findings in six workstreams:

  • Application shell foundations. The page language is declared, every view has a unique and descriptive title, a "Skip to main content" link is the first stop for keyboard users, and the interface exposes proper landmark regions (a single main area, labelled navigation, one banner) and a consistent heading structure.
  • Keyboard operability and visible focus. Every interactive control is reachable and operable by keyboard and shows a clear, consistently styled focus indicator. Data-grid sorting works from the keyboard, dialogs trap and restore focus and close on Escape, custom tooltips are dismissible, and interactive targets meet minimum size guidance.
  • Data tables. Tables expose correct row and column-header semantics so screen readers announce which column a value belongs to, and they reflow without forcing horizontal page scrolling at 200% text zoom.
  • Forms, errors, and status messages. Every input has a programmatic label, invalid entries are announced with guidance on how to correct them, and important status changes (such as a saved setting or an updated result count) are announced without moving focus.
  • Names and text alternatives. Icon-only buttons and links have descriptive names, and images carry appropriate text alternatives.
  • Colour and contrast. Text, interface controls, and status indicators meet WCAG contrast minimums in both the light and dark themes, and links within text are distinguished by more than colour alone.
Known limitations

We want to be transparent about where work remains. As of the date of this statement, we are aware of the following:

  • Some secondary and less-frequently-used views were outside the twelve-view audit sample and have not yet been individually verified to the same depth; we are extending coverage to them.
  • Third-party integration screens rendered during a connection flow are controlled by the integration provider and may not meet the same standard.
  • Highly dynamic or data-dense components are subject to continued screen-reader testing as we broaden our automated and manual coverage.

If you encounter a barrier that isn't listed here, please tell us (see Feedback and contact) — real-world reports directly shape our priorities.

How we test

Accessibility is verified continuously, not just at release:

  • Independent audit. A third-party expert evaluation against WCAG 2.2 AA (August 2026), used as the baseline for remediation.
  • Automated checks in continuous integration. Every change runs an automated accessibility sweep (axe-core) across primary views in both light and dark themes, plus lint rules that block common regressions such as an image without a text alternative or an unnamed control. A change cannot merge if these checks fail.
  • Manual testing. Keyboard-only walkthroughs and screen-reader spot checks (for example, VoiceOver and NVDA) of primary workflows.
Compatibility

The application is designed to work with recent versions of major browsers (Chrome, Edge, Firefox, and Safari) and common assistive technologies, including screen readers (such as NVDA, JAWS, and VoiceOver), screen magnification, and keyboard-only operation. Accessibility depends in part on the browser and assistive technology you use; if you find a combination that behaves poorly, let us know.

Technical specifications

Accessibility of app.unified.to relies on the following technologies working with your browser and any assistive technologies installed:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

These technologies are relied upon for conformance with WCAG 2.2 Level AA.

Requesting a VPAT / Accessibility Conformance Report

A detailed Voluntary Product Accessibility Template (VPAT® 2.5) / Accessibility Conformance Report (ACR) documenting our conformance criterion-by-criterion is available to customers and prospective customers, including for procurement and public-sector requirements.

You can request the current VPAT/ACR — along with our other security and compliance documentation — through our Trust Center at app.mycroft.io/trust/unified-to.

Feedback and contact

We welcome your feedback on the accessibility of Unified.to. If you experience a barrier, need information in a different format, or want to report an issue:

Please include the page or feature involved, what you were trying to do, and — if you can — the browser and assistive technology you were using. We aim to acknowledge accessibility reports within five business days.

Assessment and this statement

This statement was prepared on 26 August 2026, based on an independent evaluation of app.unified.to conducted in August 2026 and the remediation completed since. We review it periodically and after significant changes to the application, and we update the status as our conformance evolves.