ValiqAI should work for everyone.
We help teams find accessibility problems on their own sites, so we hold ourselves to the same standard. Here’s where we stand today, including what isn’t there yet.
Last updated September 29, 2026
Accessibility at a glance
- Our target
- WCAG 2.2 Level AA
- Where we are today
- Partially conformant
- Keyboard
- Built for keyboard use
- Screen readers
- Labels, alt text, and ARIA
- Reduced motion
- Respected
- Zoom and text size
- Supported
- Testing
- Automated
- Barrier reports
- We aim to reply in 5 business days
Where we are today
Our target is WCAG 2.2 Level AA. Today, ValiqAI is partially conformant.
The standard
The Web Content Accessibility Guidelines (WCAG) 2.2 explain how to make websites work for people with visual, hearing, motor, speech, and cognitive disabilities. We aim for Level AA.
Partially conformantIn progress
Some parts of ValiqAI don’t fully meet the standard yet. We’re an early product under active development, and we close gaps as we find them.
How we test
Our testing is automated. Code checks during development flag some common problems, such as images without alt text and invalid ARIA attributes. When someone reports a barrier, we use that report to find and fix it.
Standards we reference
WCAG 2.2 Level AA builds on WCAG 2.0 and 2.1, the versions most accessibility laws point to, including the ADA, Section 508, and the EU’s EN 301 549. This statement is for transparency, not a legal claim of compliance with any specific regulation.
What we do
Accessibility is part of how we design and build every feature.
Works with a keyboard
We build with semantic HTML and controls you can use with a keyboard, with visible focus and a logical order.
Screen reader support
Descriptive labels, alt text, and ARIA attributes help assistive technology understand the interface. Form fields are linked to their labels.
Color and contrast
We aim for enough contrast and never rely on color alone. Status and errors also use text and icons.
Your settings
We respect your system’s reduce motion setting, and the interface works with browser zoom and larger text.
What it works with
Recent browsers and common assistive technology.
Browsers
Recent versions of Chrome, Firefox, Safari, and Edge, on desktop and mobile.
Screen readers
We aim to work with VoiceOver on macOS and iOS, NVDA and JAWS on Windows, and TalkBack on Android.
Zoom and motion settings
Browser zoom, text scaling, and your system’s reduce motion setting.
Older software
Accessibility may be worse on outdated or unsupported browsers and assistive technology.
Known limitations
What doesn’t fully work yet. Your reports help us decide what to fix first.
Charts and animations
Some charts and animated visuals don’t have a full text alternative yet.
Session replays
The replay viewer is a rich, interactive screen that can be hard to use with a screen reader.
Other companies’ content
Some parts rely on outside services, like payment and sign-in providers. We can’t control their accessibility, but we consider it when choosing them.
If something blocks you
Tell us, and we’ll help you find another way to finish what you were doing.
Report a barrier
If something on ValiqAI gets in your way, or you need content in another format, tell us.
Email abhi@valiqai.comWhat to include
- The page or feature involved
- What you were trying to do
- Your browser and any assistive technology you use
What happens next
We aim to reply within five business days, and we’ll keep you updated until it’s fixed.
Need another format?
If you need something from ValiqAI in a different format, email us and we’ll help.
Not happy with our answer?
Reply to our email and ask us to review it again. We take every report seriously.