Our commitment
Accessibility is part of the product we build. ValiqAI helps teams find and fix accessibility issues on their own websites, so we hold ourselves to the same standard. We are committed to making ValiqAI usable by everyone, including people with disabilities, and to treating accessibility as an ongoing practice rather than a one-time checkbox.
This statement explains the standard we aim for, how we test against it, what is known to fall short today, and how to reach us if something gets in your way.
Conformance status
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, speech, and cognitive disabilities.
ValiqAI is currently partially conformant with WCAG 2.1 Level AA. "Partially conformant" means some parts of the product do not yet fully meet the standard. We are an early-stage product under active development, and we are closing gaps as we find them.
What we do
- •Semantic, keyboard-navigable UI: We build with semantic HTML and interactive components that can be operated with a keyboard, with visible focus states and a logical focus order.
- •Screen reader support: We use descriptive labels, alt text, and ARIA attributes so assistive technologies can interpret the interface, and we associate form fields with their labels.
- •Color and contrast: We aim for sufficient color contrast and avoid relying on color alone to convey meaning, so status and errors are also communicated through text and icons.
- •Respecting user preferences: We honor the operating system "reduce motion" setting to limit non-essential animation, and the interface supports browser zoom and text resizing.
- •Ongoing review: Accessibility is considered as we design and build new features, and we fix issues as we find them.
How we test
We evaluate accessibility using a combination of methods:
- •Automated checks during development to catch common issues like missing labels, low contrast, and invalid ARIA.
- •Manual keyboard testing to confirm that key flows can be completed without a mouse.
- •Screen reader spot-checks on primary flows using the assistive technologies listed below.
Compatibility
ValiqAI is designed to work with recent versions of major browsers (Chrome, Firefox, Safari, and Edge) on desktop and mobile. We aim for compatibility with common assistive technologies, including:
- •VoiceOver on macOS and iOS
- •NVDA and JAWS on Windows
- •TalkBack on Android
- •Browser zoom, text scaling, and OS-level reduce-motion settings
Accessibility may be degraded on unsupported or significantly outdated browsers and assistive technologies.
Known limitations
ValiqAI is under active development, and some areas may not yet fully meet our target standard. Known limitations include:
- •Data visualizations: Some charts and animated visualizations may not yet expose a full text alternative.
- •Session replays: The replay viewer is a rich, interactive surface that can be difficult to navigate with a screen reader.
- •Third-party content: Some embedded or third-party components may not fully match our accessibility target (see below).
We are working to improve these areas over time, and we welcome feedback that helps us prioritize.
Third-party content
Some parts of the experience rely on third-party services (for example, payment and authentication providers). We do not control the accessibility of third-party content, but where we can choose between vendors we consider accessibility, and we will help you find an alternative path to complete a task if a third-party component blocks you.
Feedback
If you encounter an accessibility barrier on ValiqAI, or need content in an alternative format, please let us know at abhi@valiqai.com. Please include the page or feature involved, what you were trying to do, and the browser and assistive technology you were using so we can reproduce and address it. We aim to acknowledge accessibility reports within five business days and will keep you updated on a fix.
Escalation
If you contact us about an accessibility problem and are not satisfied with our response, you can ask us to escalate the issue by replying to our email and requesting a review. We take these reports seriously and will do our best to resolve them.
Standards we reference
Our target of WCAG 2.1 Level AA is the standard commonly referenced by accessibility laws and policies, including the Americans with Disabilities Act (ADA), Section 508 of the U.S. Rehabilitation Act, and the EN 301 549 standard used in the European Union. This statement is provided for transparency and is not a legal representation of compliance with any specific regulation.
