Explore Digital Accessibility Regulations

he Web Content Accessibility Guidelines (WCAG) are the global standard for making websites and digital content accessible to people with disabilities.

Developed by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), WCAG provides 86 testable success criteria that help website owners, web designers, and content authors create accessible websites. When an organization conforms with WCAG, they have met accessibility standards that remove barriers for users with a wide range of disabilities, including visual, hearing, motor, and cognitive disabilities.

WCAG conformance is sometimes called “WCAG compliance.” WCAG itself is not a law; however, WCAG is the de facto standard for compliance with many U.S. and global laws. With digital accessibility lawsuits remaining widespread, WCAG compliance is no longer optional—it’s a legal and business necessity.

Key insights

• WCAG compliance means meeting the Web Content Accessibility Guidelines, the international standard for digital accessibility referenced by many accessibility laws.
• WCAG 2.2 is the current version with 86 success criteria; WCAG 2.1 Level AA is the standard most frequently referenced by laws and regulations.
• The four WCAG principles are Perceivable, Operable, Understandable, and Robust (POUR).
• State and local governments must conform with WCAG 2.1 AA by April 24, 2026 under the DOJ’s ADA Title II Final Rule.
• The European Accessibility Act took effect June 2025, requiring conformance with EN 301 549—an EU standard that incorporates WCAG—for many businesses selling to EU customers.
• Accessibility audits should combine automated tools with manual testing using assistive technology.

What is WCAG compliance?

WCAG compliance means a website meets the Web Content Accessibility Guidelines—the global standard for web accessibility developed by the World Wide Web Consortium (W3C). The term “WCAG compliance” is really a misnomer: because WCAG is a standard, not a law, the technically correct term is “WCAG conformance.” However, “WCAG compliance” is widely used as a synonym for “WCAG conformance.”

The WCAG guidelines provide technical success criteria that help website owners make web content accessible to people with disabilities. This includes users who rely on screen readers, keyboard navigation, captions, and other assistive technology. When your website meets WCAG requirements, people with visual, hearing, motor, and cognitive or learning disabilities can perceive, navigate, and interact with your web pages.

WCAG version	Release date	Success criteria	Status
WCAG 2.0	December 2008	61 criteria	Still referenced in many laws
WCAG 2.1	June 2018	78 criteria (+17 new)	Current legal standard
WCAG 2.2	October 2023	86 criteria (+9 new)	Latest W3C recommendation
WCAG 3.0	In development	174 outcomes (proposed)	Expected 2028 or later

What does WCAG cover?

WCAG was originally developed for HTML content that people access through web browsers. However, the relevance of these guidelines extends far beyond traditional web pages. WCAG applies broadly to web content and technologies as long as they can be interpreted by user agents, including assistive technologies.

Content type	Examples	WCAG applies?
Websites	Public sites, intranets, web applications	Yes
Mobile apps	iOS and Android applications	Yes
Documents	PDFs, Word files, spreadsheets	Yes
Multimedia	Videos, podcasts, audio files	Yes
Email	HTML newsletters, marketing emails	Yes
Digital kiosks	Self-service terminals, ATMs	Yes
E-learning	Online courses, training modules	Yes

Laws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.

Laws referencing WCAG and related standards cover different types of digital experiences. For example, the DOJ’s ADA Title II rule specifically covers web and mobile content (including digital documents) provided by state and local governments. The European Accessibility Act applies to a wide range of consumer products and services, including e-commerce platforms, banking services, and consumer electronics. Any digital content that serves the public should follow WCAG guidelines to ensure people with disabilities can access it.

Who needs to comply with WCAG?

Almost any organization with a digital presence should comply with WCAG. Legal requirements vary by sector, but accessibility benefits all businesses.

Organization type	Legal requirement	Why comply
Federal government agencies	Section 508 (mandatory)	Required by law
State and local governments	ADA Title II (mandatory)	April 2026 deadline
Private businesses	ADA Title III (court-enforced)	Lawsuit prevention
E-commerce websites	EAA in EU (mandatory)	Market access
Healthcare providers	ADA + Section 504	Patient access
Educational institutions	ADA + Section 504	Student access
Nonprofits	ADA applies	Serve all constituents

 

Even without a specific legal mandate, website owners benefit from WCAG compliance. Accessible websites reach more users, perform better in search rankings, and reduce legal risk. Over 1 billion people worldwide have disabilities—making websites accessible expands your potential audience significantly.

Is WCAG a legal requirement in the US?

Yes, for most organizations. WCAG 2.1 Level AA is the de facto standard for web accessibility under multiple US laws, and courts consistently use WCAG as the benchmark for accessibility compliance.

The DOJ’s ADA Title II Final Rule formally adopted WCAG 2.1 Level AA for all state and local governments. This covers government websites, mobile apps, digital documents, and online services.

Entity type	Population	Compliance deadline
Large public entities	50,000+ residents	April 24, 2026
Small public entities	Under 50,000 residents	April 26, 2027
Special district governments	Any size	April 26, 2027

For private businesses, Title III of the Americans with Disabilities Act requires website accessibility based on court rulings and DOJ settlement agreements. Section 508 of the Rehabilitation Act explicitly requires WCAG compliance for federal government agencies and contractors.

Digital accessibility lawsuits remain widespread. Automated tools now generate complaints at scale, making any business with accessibility issues a potential target.

What accessibility laws require WCAG compliance?

Digital accessibility legislation worldwide references WCAG as the technical standard for compliance. Meeting WCAG requirements satisfies most accessibility regulations.

Law / regulation	Geographic scope	WCAG standard required	Compliance deadline
ADA Title II (DOJ Rule)	US state / local governments	WCAG 2.1 AA	April 2026 / 2027
ADA Title III	US private businesses	WCAG 2.1 AA (de facto standard per courts)	Ongoing
Section 508	US federal agencies	WCAG 2.0 AA	Current
European Accessibility Act	Businesses serving EU consumers	EN 301 549 (Incorporates WCAG 2.1 AA)	June 28, 2025
AODA	Ontario, Canada	WCAG 2.0 AA	Current
European Web Accessibility Directive	European Union public sector	EN 301 549 (Incorporates WCAG 2.1 AA)	Current

The European Accessibility Act (EAA) became enforceable on June 28, 2025, requiring WCAG compliance for many businesses selling digital products or services to EU customers. Penalties vary by member state—fines reach €100,000 in Germany and €250,000 in France. Non-compliant products can be removed from the market entirely.

What are the four principles of WCAG?

The four principles of WCAG—known as POUR—are Perceivable, Operable, Understandable, and Robust. These principles guide all WCAG success criteria and define what it means for web content to be accessible.

Principle	What It Means	Example Requirement
Perceivable	Users must be able to perceive content through at least one sense.	Provide text alternatives for images; add captions to videos.
Operable	Users must be able to operate the interface.	Enable keyboard access; provide enough time to read content.
Understandable	Users must understand the content and how to use it.	Use clear language; make navigation predictable.
Robust	Content must work with current and future user agents.	Use valid code; ensure compatibility with assistive technology.

What are the 13 WCAG guidelines?

The four WCAG principles contain 13 guidelines that provide specific objectives for web accessibility. Each guideline has testable success criteria at three WCAG conformance levels: A, AA, and AAA.

Perceivable guidelines

1.1 Text Alternatives — Provide text alternatives for non-text content. This includes alt text for images, labels for form fields, and descriptions for icons. Text alternatives let screen reader users understand content they cannot see.

1.2 Time-Based Media — Provide alternatives for audio and video content. This includes captions for videos, transcripts for audio files, and audio descriptions for visual content.

1.3 Adaptable — Create content that can be presented in different ways without losing information. Web pages should maintain meaning when users change display settings or use assistive technology.

1.4 Distinguishable — Make content easy to see and hear. This includes sufficient color contrast, resizable text, and audio controls. Users with low vision or hearing loss depend on these features.

Operable guidelines

2.1 Keyboard Accessible — Make all functionality available from a keyboard. Users who cannot use a mouse must be able to navigate web content using keyboard access alone.

2.2 Enough Time — Give users enough time to read and interact with content. Avoid strict time limits, or provide ways to extend them.

2.3 Seizures and Physical Reactions — Do not design content that causes seizures. Avoid flashing content that could trigger photosensitive epilepsy.

2.4 Navigable — Help users navigate and find content. Provide clear headings, descriptive link text, and logical focus order.

2.5 Input Modalities — Support different input methods beyond keyboard and mouse. Users may rely on touch screens, voice commands, or switch controls.

Understandable guidelines

3.1 Readable — Make text readable and understandable. Use clear language and define unusual terms or abbreviations.

3.2 Predictable — Make web pages appear and operate in predictable ways. Consistent navigation and functionality help all users.

3.3 Input Assistance — Help users avoid and correct mistakes. Provide clear error messages and instructions for forms.

Robust guidelines

4.1 Compatible — Maximize compatibility with current and future user agents, including assistive technologies. Use valid code and follow web standards so content works reliably across different browsers and devices.

What are the three WCAG conformance levels?

WCAG has three conformance levels—Level A, Level AA, and Level AAA—that define increasing degrees of accessibility. Level AA is the legal standard for most accessibility requirements.

Level	Description	Success Criteria	Legal Status
Level A	Minimum accessibility—addresses the most critical accessibility barriers.	30 criteria	Required for compliance
Level AA	Standard accessibility—removes barriers for most people with disabilities.	20 additional criteria	Required by most laws
Level AAA	Highest accessibility—provides enhanced access but is not always achievable.	28 additional criteria	Aspirational; not legally required

Each level builds on the previous one. To achieve Level AA, you must first meet all Level A criteria. The conformance levels help website owners prioritize accessibility efforts and understand their compliance obligations.

For WCAG compliance with most accessibility laws, organizations must meet all WCAG Level A and Level AA success criteria. Level AAA conformance is optional because some criteria cannot be met for all content types.

How success criteria differ by level

The same guideline can have success criteria at different levels. Here’s an example using video accessibility requirements:

Success Criterion	Level	Requirement
1.2.3 Audio Description or Media Alternative	A	Provide audio description or a text alternative for video.
1.2.5 Audio Description (Prerecorded)	AA	Provide audio description for all prerecorded video.
1.2.8 Media Alternative (Prerecorded)	AAA	Provide a full text transcript that includes audio descriptions.

As levels increase, the requirements become more comprehensive. Level A offers flexibility (audio description OR text), Level AA requires audio description specifically, and Level AAA requires both audio and text alternatives.

What are WCAG violations?

WCAG violations occur when web content fails to meet one or more success criteria. Each violation creates an accessibility barrier that prevents people with disabilities from using your website.

Common WCAG violations include:

Violation	WCAG Criterion	Impact
Missing alt text on images	1.1.1 Non-text Content	Screen reader users can’t understand images.
Insufficient color contrast	1.4.3 Contrast (Minimum)	Users with low vision can’t read text.
No keyboard access	2.1.1 Keyboard	Users who can’t use a mouse are blocked.
Missing form labels	1.3.1 Info and Relationships	Screen reader users can’t complete forms.
Auto-playing media	1.4.2 Audio Control	Interferes with screen readers.
No captions on videos	1.2.2 Captions (Prerecorded)	Deaf and hard-of-hearing users miss content.
Missing page titles	2.4.2 Page Titled	Users can’t identify or navigate web pages.

Any accessibility issue that prevents users from perceiving, operating, or understanding your web content is a potential WCAG violation—and a potential legal liability.

How do I make my website WCAG compliant?

Making websites accessible requires a combination of automated tools, manual testing, and ongoing accessibility efforts. No single tool catches all accessibility issues.

Step 1: Conduct an accessibility audit

Start with an accessibility audit that combines automated scanning with manual testing by experts and people with disabilities. Automated tools cannot catch all accessibility issues—the rest require human review using assistive technologies like screen readers.

Testing Method	What It Catches	Limitations
Automated tools	Common accessibility issues such as color contrast problems, missing alternative text, and missing form labels.	Cannot detect all accessibility issues.
Manual expert review	Comprehensive accessibility violations, including keyboard navigation, focus order, page structure, and semantic markup.	Experts may not experience the site the same way as real users with disabilities.
Functional assistive technology (AT) testing	Barriers encountered by assistive technology users during critical user journeys, such as registration or checkout.	Typically performed by a single assistive technology expert and does not represent all disabilities or user needs.
User testing by people with disabilities	Real-world usability challenges, including confusing layouts, navigation issues, and frustrating task completion.	May require additional planning, coordination, and resources.

Step 2: Fix accessibility issues by priority

Focus on issues that create the biggest accessibility barriers for users. These are also the most likely to expose you to legal risk.

Step 3: Train your team

Web designers, developers, and content creators all play a role in accessibility. Train everyone involved in creating digital content on WCAG requirements and accessibility standards.

Step 4: Build accessibility into your process

Don’t retrofit accessibility—build it in from the start. Include accessibility requirements in design specs, code reviews, and content guidelines. This approach costs less and produces better results than fixing accessibility issues after launch.

Step 5: Document your accessibility efforts

Publish an accessibility statement on your website. Document your conformance claims, known issues, and remediation timeline. This demonstrates good faith and may reduce penalties if issues arise.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 builds on WCAG 2.1 and is fully backwards compatible. Content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0.

Feature	WCAG 2.1	WCAG 2.2
Release date	June 2018	October 2023
Total success criteria	78	86
New success criteria	17 (added to WCAG 2.0)	9 (added to WCAG 2.1; one previous criterion removed)
Focus areas	Mobile accessibility, low vision, and cognitive accessibility.	Cognitive disabilities, low vision, and mobile accessibility.
Legal status	Current standard for most accessibility laws.	Recommended standard that is increasingly becoming a legal requirement.

WCAG 2.2 added nine new success criteria focused on users with cognitive or learning disabilities, people with low vision, and mobile device users. Key additions include requirements for focus appearance, dragging movements, and accessible authentication.

Most accessibility regulations currently reference WCAG 2.1, but organizations should target WCAG 2.2 to future-proof their accessibility compliance. The existing success criteria from 2.1 remain unchanged in 2.2 with the exception of one criterion which was removed.

What about WCAG 3.0?

WCAG 3.0 is the next major version of the accessibility guidelines. The Accessibility Guidelines Working Group continues developing the standard, but no formal date has been set for its release.

WCAG 3.0 introduces significant changes including a new scoring system (0-4 scale instead of pass/fail), new conformance levels (Bronze / Silver / Gold instead of A / AA / AAA), and broader scope covering newer technologies like voice interfaces and wearable devices.

Organizations should continue targeting WCAG 2.2 AA as the operative standard. WCAG 3.0 won’t affect legal requirements for years, but its concepts—like user testing with assistive technology—are worth adopting now.