WCAG Pulse is an automated web accessibility testing platform that scans websites for WCAG 2.1 and WCAG 2.2 compliance issues using the axe-core engine. It provides detailed reports with specific element selectors, code snippets, and actionable fix recommendations.

What accessibility standards does WCAG Pulse support?

WCAG Pulse supports WCAG 2.0, WCAG 2.1, and WCAG 2.2 at all conformance levels (A, AA, AAA). It also helps with Section 508, ADA Title III, and EN 301 549 compliance requirements.

How much does WCAG Pulse cost?

WCAG Pulse offers a Free plan (100 pages/month, 1 site), Starter at $35/month (500 pages, 3 sites), Pro at $79/month (2,500 pages, 10 sites, Slack integration), and Business at $199/month (12,000 pages, 50 sites, API access). Annual billing saves 17%.

What accessibility issues can WCAG Pulse detect?

WCAG Pulse detects issues including: missing alt text, insufficient color contrast, missing form labels, keyboard accessibility problems, ARIA attribute errors, heading structure issues, missing document language, and many more automated checks powered by axe-core.

Can I integrate WCAG Pulse with my CI/CD pipeline?

Yes, WCAG Pulse provides a RESTful API (available on Pro and Business plans) that can be integrated with GitHub Actions, GitLab CI, Jenkins, and other CI/CD tools to automate accessibility testing as part of your deployment workflow.

How accurate is WCAG Pulse scanning?

WCAG Pulse uses axe-core, which has a zero false-positive guarantee for detected issues. Automated testing covers approximately 60% of WCAG criteria. For complete WCAG 2.2 compliance, we recommend combining automated testing with manual review.

ADA Website Accessibility Compliance Guide
The Americans with Disabilities Act (ADA) is a United States civil rights law enacted on July 26, 1990. It prohibits discrimination against individuals with disabilities in all areas of public life. In the context of digital accessibility, ADA requirements have become one of the most significant drivers of website accessibility compliance worldwide.

What Is the ADA?
The ADA was signed into law by President George H.W. Bush on July 26, 1990. It is divided into five titles:
Title I — Employment

Title II — State and Local Government Services

Title III — Public Accommodations and Commercial Facilities

Title IV — Telecommunications

Title V — Miscellaneous Provisions
For website accessibility, Title II and Title III are the most relevant.
ADA Title II: Government Websites
Title II of the ADA applies to state and local government entities. On April 24, 2024, the U.S. Department of Justice (DOJ) published a final rule updating its Title II regulations to include specific technical requirements for web content and mobile applications.
Technical Standard Required
The DOJ rule explicitly requires conformance with WCAG 2.1 Level AA (Web Content Accessibility Guidelines Version 2.1, Level AA) as published by the World Wide Web Consortium (W3C).
Compliance Deadlines
The compliance deadlines depend on the population served:
What Is Covered
The rule applies to web content and mobile applications that a state or local government entity provides or makes available, directly or through a third party, to members of the public or to government employees for use in the performance of their job duties.
ADA Title III: Private Businesses
Title III of the ADA covers places of public accommodation, which includes businesses open to the public. While the DOJ has not yet issued a specific Title III rule for website accessibility, courts across the United States have increasingly applied Title III to websites.
Current Legal Landscape
Federal Circuit Courts currently take different approaches:
The 1st Circuit holds that websites offering goods or services directly to the public can qualify as places of public accommodation, even for online-only businesses.

The 3rd, 5th, 6th, and 9th Circuits require a sufficient "nexus" between the website and a physical location.

The 2nd, 7th, and 11th Circuits have generally found websites to be covered under Title III.
In practice, courts and regulators have pointed to WCAG 2.1 Level AA as the appropriate technical standard for Title III compliance.
Lawsuit Statistics
ADA website accessibility lawsuits have become a significant concern for businesses:
In 2024, over 4,000 ADA website accessibility lawsuits were filed across state and federal courts in the United States.

E-commerce websites are the primary target, representing approximately 77% of filed lawsuits.

The first half of 2025 saw over 2,000 lawsuits filed, projecting nearly 5,000 by year-end.

New York, California, and Florida account for the majority of filed cases.
Most Targeted Industries
Based on 2024 lawsuit data, the industries most frequently targeted by ADA website accessibility lawsuits include:
Fashion, Clothing, and Apparel — Largest share of lawsuits

Restaurant, Food, and Beverages — Online ordering and menu accessibility

Beauty and Personal Care — E-commerce accessibility

Healthcare and Medical — Patient portal and information accessibility

Home Furnishings and Retail — Product catalog accessibility
What WCAG 2.1 Level AA Requires
WCAG 2.1 Level AA includes 50 success criteria organized under four principles:
Perceivable
Content must be presentable to users in ways they can perceive. This includes providing text alternatives for non-text content, captions for multimedia, and sufficient color contrast.
Operable
User interface components and navigation must be operable. This includes keyboard accessibility, adequate time for users to read and use content, and clear navigation mechanisms.
Understandable
Information and the operation of the user interface must be understandable. This includes readable text, predictable behavior, and input assistance to help users avoid and correct mistakes.
Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This includes proper use of HTML markup and compatibility with current and future tools.
How WCAG Pulse Helps with ADA Compliance
WCAG Pulse provides automated accessibility testing against WCAG 2.0, 2.1, and 2.2 standards at all conformance levels (A, AA, AAA). The platform helps organizations:
Monitor compliance continuously with scheduled scans that detect accessibility issues as they arise.

Track issues by WCAG criterion to understand exactly which success criteria are affected.

Generate compliance reports with detailed information about detected violations and recommended fixes.

Prioritize remediation with severity-based issue categorization (critical, major, minor).

Demonstrate ongoing commitment with accessibility badges and scan history records.
Automated testing tools such as WCAG Pulse can detect approximately 30-40% of WCAG success criteria violations. For comprehensive ADA compliance, organizations should combine automated scanning with manual expert audits and assistive technology testing.
Steps to Achieve ADA Compliance
Audit your website — Run an automated accessibility scan to identify existing issues.

Prioritize critical issues — Address critical and major violations first, focusing on barriers that prevent users from completing essential tasks.

Implement fixes — Work with developers to resolve identified issues following WCAG 2.1 Level AA success criteria.

Publish an accessibility statement — Communicate your commitment to accessibility and provide a mechanism for users to report barriers.

Monitor continuously — Use automated scanning tools to detect new issues as your website content changes.

Conduct manual audits — Supplement automated testing with manual expert reviews and user testing with assistive technologies.
Related Resources
Section 508 Compliance Guide

EN 301 549 European Standard

European Accessibility Act (EAA)

AODA and Canadian Accessibility

Accessibility by Industry

ADA Title II: Government WebsitesTitle II of the ADA applies to state and local government entities. On April 24, 2024, the U.S. Department of Justice (DOJ) published a final rule updating its Title II regulations to include specific technical requirements for web content and mobile applications.

Technical Standard RequiredThe DOJ rule explicitly requires conformance with WCAG 2.1 Level AA (Web Content Accessibility Guidelines Version 2.1, Level AA) as published by the World Wide Web Consortium (W3C).

Compliance DeadlinesThe compliance deadlines depend on the population served:

What Is CoveredThe rule applies to web content and mobile applications that a state or local government entity provides or makes available, directly or through a third party, to members of the public or to government employees for use in the performance of their job duties.

What WCAG 2.1 Level AA RequiresWCAG 2.1 Level AA includes 50 success criteria organized under four principles:

PerceivableContent must be presentable to users in ways they can perceive. This includes providing text alternatives for non-text content, captions for multimedia, and sufficient color contrast.

OperableUser interface components and navigation must be operable. This includes keyboard accessibility, adequate time for users to read and use content, and clear navigation mechanisms.

UnderstandableInformation and the operation of the user interface must be understandable. This includes readable text, predictable behavior, and input assistance to help users avoid and correct mistakes.

RobustContent must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This includes proper use of HTML markup and compatibility with current and future tools.

Related ResourcesSection 508 Compliance Guide EN 301 549 European Standard European Accessibility Act (EAA) AODA and Canadian Accessibility Accessibility by Industry

Contact Sales Team

ADA Title II: Government Websites
Title II of the ADA applies to state and local government entities. On April 24, 2024, the U.S. Department of Justice (DOJ) published a final rule updating its Title II regulations to include specific technical requirements for web content and mobile applications.

Technical Standard Required
The DOJ rule explicitly requires conformance with WCAG 2.1 Level AA (Web Content Accessibility Guidelines Version 2.1, Level AA) as published by the World Wide Web Consortium (W3C).

Compliance Deadlines
The compliance deadlines depend on the population served:

What Is Covered
The rule applies to web content and mobile applications that a state or local government entity provides or makes available, directly or through a third party, to members of the public or to government employees for use in the performance of their job duties.

What WCAG 2.1 Level AA Requires
WCAG 2.1 Level AA includes 50 success criteria organized under four principles:

Perceivable
Content must be presentable to users in ways they can perceive. This includes providing text alternatives for non-text content, captions for multimedia, and sufficient color contrast.

Operable
User interface components and navigation must be operable. This includes keyboard accessibility, adequate time for users to read and use content, and clear navigation mechanisms.

Understandable
Information and the operation of the user interface must be understandable. This includes readable text, predictable behavior, and input assistance to help users avoid and correct mistakes.

Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This includes proper use of HTML markup and compatibility with current and future tools.

Related Resources
Section 508 Compliance Guide

EN 301 549 European Standard

European Accessibility Act (EAA)

AODA and Canadian Accessibility

Accessibility by Industry