Our Commitment
Worxley is used by sales and operations teams every day, and we want that to be true regardless of how someone navigates the web — with a mouse, a keyboard, a screen reader, or other assistive technology.
Accessibility is an ongoing effort, not a one-time checklist. We review it as we build new features, not only when something is flagged.
Standard We Target
We design and test Worxley with the goal of conforming to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.
What We've Built
Some of what's already in place across the platform:
- Keyboard navigation: Core workflows — including forms, dropdowns, and dialogs — are operable without a mouse, with visible focus states.
- Semantic structure: Pages use semantic HTML and ARIA landmarks so screen readers can navigate headings, forms, and regions predictably.
- Colour contrast: Text and interactive elements are designed to meet WCAG AA contrast ratios against their backgrounds.
- Responsive text: Layouts adapt to browser zoom and text-size settings without breaking or clipping content.
- Accessible forms: Form fields carry associated labels and error messages so assistive technology can announce them correctly.
Known Limitations
Some areas of the product — particularly data-dense views like pipeline boards and dashboards — are still being improved for full keyboard and screen-reader support.
If you encounter a barrier using Worxley with assistive technology, please tell us. Your report directly shapes what we prioritize next.
Feedback & Contact
We welcome feedback on the accessibility of Worxley. If you encounter an accessibility barrier, let us know what page you were on, what assistive technology you were using, and what happened.