Accessibility is an important part of how we design and develop Onedash. We want our website, platform, and applications to be usable by as many people as reasonably possible, including people who use assistive technologies or interact with software in different ways. Accessibility is an ongoing process, and as Onedash develops, we continue to review our interfaces, components, content, and interaction patterns and make improvements where accessibility issues are identified.

1. Our Accessibility Goals

We aim to progressively align our web-based experiences with the Web Content Accessibility Guidelines ("WCAG") 2.2 and to apply the same accessibility principles where reasonably practicable across the Onedash desktop application. Our goal is to work toward WCAG 2.2 Level AA across the parts of Onedash that are within our control. We do not currently represent that every part of the Services fully conforms to WCAG 2.2 or has been independently certified for accessibility.

2. Our Accessibility Principles

2.1 Build Accessibility In

We consider accessibility as part of product design and development rather than treating it only as a final compliance check. Where appropriate, this includes considering semantic structure, keyboard access, focus behaviour, readable text, colour contrast, form labelling, error messaging, screen reader support, responsive layouts, and interaction patterns that do not unnecessarily depend on a particular input method.

2.2 Use Accessible Components

We aim to use consistent interface components and patterns that support accessible interaction across the Services. Where issues are identified in shared components, we aim to address them in a way that improves accessibility throughout the product.

2.3 Test and Improve

We use a combination of development review, automated tooling, browser testing, keyboard testing, and manual review where appropriate to help identify accessibility issues. Automated testing cannot identify every accessibility issue, so accessibility also requires ongoing design, development, and manual review.

2.4 Support Different Ways of Using Onedash

We recognise that people interact with software using different devices, input methods, display settings, browsers, operating systems, and assistive technologies. We aim to avoid unnecessary barriers that prevent people from accessing important functionality.

3. Third-Party Services and Content

Onedash may display, connect to, or provide access to third-party websites, applications, services, and content. We do not control the accessibility of third-party services or content and cannot guarantee that they meet the same accessibility goals that we apply to Onedash. Where an accessibility issue originates from a third-party service, we may have limited ability to correct the underlying issue directly.

4. Current Status

Onedash is actively being developed and our accessibility work is ongoing. Some parts of the Services may not yet fully meet our accessibility goals. We have not currently completed a formal independent accessibility certification or audit of the entire Onedash platform. As the platform develops, we intend to continue reviewing accessibility and addressing significant issues as they are identified.

5. Accessibility Feedback

If you experience an accessibility issue while using Onedash, we want to hear about it. Reports help us identify barriers that may not have been discovered during development or testing. When reporting an accessibility issue, it is helpful to include the page, feature, or part of the application affected, what you were trying to do, and any relevant browser, operating system, device, or assistive technology information.

You can report accessibility issues to [email protected].

6. Ongoing Improvement

Accessibility requirements, technologies, and best practices continue to evolve. We may update this statement as Onedash changes, our accessibility practices develop, or applicable standards and requirements are updated.