Accessibility Statement

Last updated: April 16, 2026

Our commitment

Vaquill AI is committed to digital accessibility so that lawyers with disabilities can use our legal research tools effectively, independently, and on equal footing with their peers. We believe that accessible software is better software for everyone.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. WCAG 2.2 was finalized by the W3C in October 2023 and is the current recommendation. It is also the standard the US Department of Justice has adopted for Title II web-accessibility requirements for state and local government entities.

Conformance status: Partially conformant. “Partially conformant” means that some parts of the content do not fully conform to the accessibility standard. We are continuously working to improve, and we will not overclaim full conformance until Vaquill AI has been reviewed by a qualified external accessibility auditor.

Measures we take

Accessibility is part of how we build Vaquill AI, not an afterthought. Specifically:

  • Accessibility is considered during both design and development, not bolted on at the end.
  • Automated accessibility checks run in our continuous integration pipeline. (We currently lean on Deque axe-core style tooling.)
  • Manual keyboard-only testing on new pages and interactive components before release.
  • Testing with major screen readers, including NVDA and JAWS on Windows and VoiceOver on macOS and iOS.
  • A full external accessibility review is on our roadmap.

Technical specifications

Vaquill AI relies on the following technologies to work with the particular combination of web browser and assistive technologies or plugins installed on your computer:

  • HTML
  • CSS
  • JavaScript (React and Next.js)

These technologies are relied upon for conformance with the accessibility standards used.

Tested browsers

We test Vaquill AI against the latest two major versions of each of the following browsers:

  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge

Assistive technologies supported

  • Screen readers: NVDA, JAWS, and VoiceOver (macOS and iOS)
  • Voice control: Dragon NaturallySpeaking, macOS Voice Control, Android Voice Access
  • Keyboard-only navigation, including standard tab order, skip links, and visible focus indicators
  • Operating-system-level zoom and browser text resizing up to 200%

Known limitations

Despite our best efforts, some content and features on Vaquill AI do not yet fully meet WCAG 2.2 AA. We want to be upfront about these so that you can plan around them and tell us when they cause problems. Known issues include:

  • PDF case exports. Some PDFs generated from our case law corpus may not be fully tagged for screen readers. We are rolling out server-side remediation so that exported PDFs include proper structure, headings, and reading order.
  • Third-party embeds. Embedded demo videos (for example, YouTube players) inherit the accessibility characteristics of the upstream provider. Captions and transcripts depend on that provider's tooling. Where we control the source video, we publish captions.
  • Historical blog post images. We are backfilling descriptive alt text on older blog posts. Newer posts are authored with meaningful alt text from the start.
  • Complex research visualizations. Interactive citation graphs and chronology timelines are being updated so that every view also offers an equivalent accessible table or list representation.

Assessment approach

Vaquill AI assesses the accessibility of our website in the following ways:

  • Self-evaluation against the WCAG 2.2 Level AA success criteria.
  • Automated scanning with Deque axe-core style tooling integrated into our build process.
  • Manual review by engineers using keyboard-only navigation and screen readers during feature development.

A note on accessibility overlays

Vaquill AI does not use third-party accessibility overlays, toolbars, or widgets that claim to make a site compliant by adding a script. Independent testing and guidance from disability advocates have repeatedly shown that overlays often fail to remediate underlying issues, can interfere with users' own assistive technology, and are frequently named in US ADA Title III lawsuits. We prefer to fix accessibility problems at the source in our code.

How to report accessibility issues

We welcome your feedback on the accessibility of Vaquill AI. If you encounter an accessibility barrier, please let us know:

When you report an issue, it helps us reproduce and fix it faster if you include:

  • The URL of the page where you encountered the problem
  • A description of the issue and what you expected to happen
  • The assistive technology you were using (screen reader, voice control, etc.) and its version
  • Your browser and operating system

We aim to acknowledge every report within 2 US business days and to provide a substantive response within 10 US business days. For critical blockers that prevent you from using the product, we will prioritize a fix or a documented workaround.

Formal complaints

If you are not satisfied with our response, you may pursue a formal complaint. In the United States, you may contact your state attorney general's office, or file a complaint with the US Department of Justice under Title III of the Americans with Disabilities Act. We would prefer the chance to resolve the issue directly first, but we respect your right to seek independent review.

Related policies

Commitment to improvement

Accessibility is not a one-time project. It is an ongoing practice that improves with every release, every bug report, and every conversation with the people who use Vaquill AI. If something here is outdated, or if your experience does not match what this statement describes, we want to hear about it so we can do better.

Quick link: Report an accessibility issue at contact@vaquill.ai. We acknowledge reports within 2 business days.