Accessibility

TradeAnchor Desk aims to be usable by everyone, including people with disabilities, on a phone, on a laptop, in the field, and in real lighting.

Our commitment

TradeAnchor Desk is designed with web accessibility as an ongoing goal. We work toward the relevant principles of the Web Content Accessibility Guidelines (WCAG 2.1, level AA) - perceivable, operable, understandable, and robust - and toward the goals of the Americans with Disabilities Act (ADA) for accessible digital experiences. We continue to improve accessibility as the product develops.

What we support today

  • Keyboard navigation across forms, dialogs, and pipeline pages.
  • Screen-reader compatible labels on inputs, buttons, and navigation.
  • Clear semantic headings on every page.
  • Alt text on meaningful icons and images; decorative icons are hidden from screen readers.
  • Readable type sizes and high contrast across the interface.
  • Mobile-responsive layout with large tap targets for field use.
  • Error messages that name the field and explain what to fix.
  • Status colors paired with text labels so meaning is not carried by color alone.
  • Focus styles that remain visible when navigating by keyboard.
  • Modal dialogs that trap focus and restore it on close.

Known limitations

  • Some pipeline drag interactions are easier with a mouse or touchscreen than with a keyboard.
  • Animated indicators in the dashboard do not yet honor the "reduced motion" setting consistently.

We are actively working to improve these areas.

Report an accessibility issue

If something is hard to read, hard to tap, or hard to navigate - or if you are blocked from completing a task with assistive technology - please tell us. Visit Contact Support and choose the "Technical issue" topic. Include the page you were on, the device or assistive technology you were using, and what you were trying to do.

Third-party content

Some parts of the app rely on third-party services (for example authentication providers). We work to choose providers that prioritize accessibility, but we may not control every aspect of their interface. If you hit a barrier in a third-party component, tell us and we will route it to the provider when needed.

This document is beta template language and should be reviewed by a qualified attorney before public launch. Nothing in this document is legal advice.