Web accessibility for every business, from scan to compliance.

Title III of the Americans with Disabilities Act (ADA) covers businesses that are open to the public, and courts have applied it to websites. Title III does not name a technical standard, so WCAG 2.1 or 2.2 at level AA is the benchmark used in most lawsuits, demand letters and settlements.

For state and local governments, a 2024 Department of Justice rule under Title II sets WCAG 2.1 AA as the required standard. Federal agencies and their vendors follow Section 508.

For more, read our ADA compliance guide.

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility, published by the W3C. They are organized under four principles: content must be perceivable, operable, understandable and robust.

Each guideline has success criteria at three levels, A, AA and AAA. Level AA is the target in most laws and lawsuits, including ADA cases, Section 508 and the European Accessibility Act. The latest version is WCAG 2.2.

See our WCAG guide for the full picture.

Don’t ignore it. Demand letters usually cite specific barriers on your site, so the first step is a technical analysis of those issues against WCAG.

From there, fix the issues, document the work and keep monitoring the site so new barriers don’t appear. Our litigation support reviews the claim, remediates the issues it cites and provides the technical documentation your legal team needs. It does not replace advice from your lawyer.

A widget gives visitors useful controls, such as text size, contrast and keyboard navigation. On its own, though, it doesn’t fix problems in your site’s code, such as missing labels or a broken focus order.

For WCAG conformance, pair it with testing and remediation: a manual audit, managed manual remediation, or the AI Accessibility Agent, which finds issues and applies fixes for you.

The cost depends on the size of your site, its platform, its current state and how much your own team takes on. A well-built site needs less work; older or more complex sites need more manual fixes.

You can start with our free tools and the AI agent’s free plan, then move to a paid plan or a managed service as your needs grow. See pricing for every plan.

Yes. PDFs and documents you publish on your site are part of it, and ADA claims can include them. An accessible PDF needs tags, a correct reading order, alt text and labeled form fields to meet WCAG and PDF/UA.

Our PDF remediation fixes documents with AI and delivers a report after each one.

Automated scans quickly find issues that can be detected in code, such as missing alt text, low contrast or empty buttons, and they can run on every page, every month.

Many issues need a person: a confusing focus order, unclear link text, or a form that a screen reader can’t complete. Our specialists test with screen readers, zoom and keyboard navigation. A complete approach uses both.

Yes. tabnav accessibility monitoring connects to Claude and other AI assistants that support MCP (Model Context Protocol). Ask for a scan in the chat and the results come back right there, ready for your assistant to help you fix.

With tunneling, you can scan your local build through a secure tunnel, fix issues and check them again before you deploy, instead of waiting for every release.

Yes. You can start today with our free tools:

• Accessibility checker: an instant report on WCAG, ADA and EAA issues.
• Free accessibility widget: essential accessibility controls for your visitors.
• Free accessibility monitor: track one page and its issues over time.
• Contrast checker: check text, links and images against WCAG contrast rules.