WCAG
Compliance
- WCAG (Web Content Accessibility Guidelines) is the global standard for digital accessibility
- WCAG provides a framework for making websites, applications, and digital content accessible
- WCAG compliance means meeting testable accessibility success criteria for all WCAG guidelines
- WCAG is organized around four principles: perceivable, operable, understandable, and robust (POUR)
- WCAG is widely used to support compliance with accessibility laws such as ADA, Section 508, and the European Accessibility Act
On This Page
How to prepare for the May HHS accessibility deadline
What is WCAG?
The Web Content Accessibility Guidelines (WCAG) are the global standard for digital accessibility and provide a framework for how websites, applications, and digital content should be designed and developed to be accessible to people with disabilities. Developed by the World Wide Web Consortium (W3C), WCAG provides a widely accepted framework for creating digital experiences that can be accessed and used by a broad range of users.
WCAG is the most widely referenced benchmark for accessibility and is commonly used to support compliance with laws and regulations. By following WCAG guidelines and meeting WCAG success criteria, organizations can ensure that digital content is usable across different devices, environments, and assistive technologies.
Organizations use WCAG to evaluate accessibility, guide remediation, and support compliance with digital accessibility requirements.
What is WCAG compliance?
At a high level, WCAG compliance refers to meeting the accessibility criteria defined in the Web Content Accessibility Guidelines. In practice, this means ensuring that websites, applications, and digital content are accessible, usable, and functional for people with disabilities across a range of real-world scenarios.
While the term “WCAG compliance” is commonly used, the more technically accurate term is WCAG conformance. Conformance refers to how well a digital experience meets the requirements of a technical standard. Conformance is measurable and used to evaluate accessibility against specific WCAG success criteria. Compliance relates to the extent to which organizations meet applicable laws and regulations. Many organizations use the terms interchangeably, but both relate to achieving accessible digital experiences aligned with WCAG guidelines.
Achieving WCAG compliance involves more than meeting technical requirements. Digital content must be usable with assistive technologies such as screen readers and magnifiers, and support users with a range of needs, including visual, auditory, cognitive, and mobility impairments. When accessibility is built into how digital experiences are designed, developed, and maintained, organizations are better positioned to maintain WCAG conformance success criteria over time.
What are WCAG standards and guidelines?
The Web Content Accessibility Guidelines (WCAG) is a set of guidelines organized into testable success criteria.
Some organizations refer to “WCAG standards” as the collective set of guidance provided by WCAG.
WCAG guidelines provide high-level guidance that forms a foundation for building digital accessibility across websites, applications, and other digital systems. The guidelines describe how web content should be presented, structured, and interacted with to support the accessibility needs of people with disabilities.
WCAG guidelines are supported by specific success criteria that can be measured and tested, allowing organizations to assess how well their content aligns with WCAG compliance. Together, WCAG standards provide a consistent framework for building and maintaining accessible digital content, allowing flexibility in how accessibility is implemented based on the purpose and target audience of a website.
WCAG versions: 2.0, 2.1, 2.2, and 3.0
The Web Content Accessibility Guidelines (WCAG) have evolved over time to address changes in technology and user needs. Each version builds on the previous one, expanding coverage and refining how WCAG compliance is achieved.
WCAG 2.0
Replacing WCAG 1.0, WCAG 2.0 established the foundation for modern accessibility by introducing the core structure of testable success criteria and the POUR principles. It remains the baseline referenced by many regulations and policies.
WCAG 2.1
Expanded WCAG 2.0 by adding requirements that address mobile accessibility, low vision, and cognitive disabilities, making WCAG compliance more applicable across devices and user needs.
WCAG 2.2
Introduced additional success criteria focused on meeting the needs of users with cognitive disabilities and mobility limitations, further strengthening WCAG guidelines. WCAG 2.2. Also removed one success criterion from WCAG 2.1, which was considered no longer applicable given the evolution of technology.
WCAG 3.0 (in development)
Initially known as Project Silver, WCAG 3.0 is being developed as a more flexible and comprehensive approach to accessibility. It aims to simplify how WCAG standards are applied while expanding coverage across a broader range of technologies and user experiences and providing more flexible ways to measure conformance. At the time of writing, WCAG 3.0 is still several years from completion.
Each version can be explored in more detail to understand specific requirements and how they impact WCAG compliance across digital systems.
WCAG conformance levels: A, AA, AAA
WCAG uses three conformance levels—A, AA, and AAA—to indicate how accessible a digital experience is based on which WCAG success criteria are satisfied at each level. These WCAG conformance levels help organizations measure progress toward WCAG compliance and define accessibility goals.
Level A (minimum)
Level A represents the most basic level of accessibility and addresses the most critical barriers. Meeting this level addresses some critical barriers, but it does not provide a complete or consistent accessible experience.
Level AA (recommended standard)
Level AA is the most widely accepted target for WCAG compliance and is required by many regulations and policies around the world. It addresses a broader range of accessibility needs and supports compatibility with commonly used assistive technologies. Most organizations aim to meet WCAG AA to achieve meaningful accessibility.
Level AAA (advanced)
Level AAA represents the highest level of accessibility and provides the most inclusive user experience. However, conformance at this level is not always practical or feasible for all content, so many organizations focus on Level AA while incorporating as many AAA criteria as possible.
Together, these WCAG compliance levels provide a structured way to evaluate accessibility and guide organizations in following WCAG guidelines in a consistent and measurable way.
WCAG principles (POUR)
The Web Content Accessibility Guidelines (WCAG) are built on four foundational principles: perceivable, operable, understandable, and robust—often referred to as POUR. These WCAG principles define how digital content must function to support accessibility and guide how organizations achieve WCAG compliance in practice.
Perceivable
Information and user interface components must be presented in ways that users can perceive, whether by sight, sound, touch, or other senses. This includes providing alternatives for non-text content and ensuring that content can be seen or heard in different ways.
Operable
User interface components and navigation must be usable through a variety of inputs. Users should be able to interact with content without requiring actions they cannot perform, such as relying only on a mouse.
Understandable
Content and interactions must be clear and predictable without requiring significant cognitive demands. Users should be able to understand information, interact with digital experiences without undue confusion or unnecessary complexity, and recover from errors with the minimum effort.
Robust
Content must be compatible with current and future technologies, including assistive technologies. This ensures that digital experiences remain accessible as tools and platforms evolve.
Together, these principles provide a framework for designing, developing, and maintaining accessible digital content that supports a wide range of users and technologies.
Who needs to follow WCAG?
While the Web Content Accessibility Guidelines (WCAG) are not a law on their own, they are widely used to meet legal and regulatory accessibility requirements. When applied, organizations follow WCAG standards to achieve WCAG compliance and demonstrate that their digital experiences are accessible.
WCAG is commonly used to support compliance with:
- Americans with Disabilities Act (ADA)
WCAG is used to evaluate and support compliance with ADA Title II requirements. WCAG compliance is also recommended for private companies to demonstrate compliance with Title III of the ADA. - Section 508
U.S. federal accessibility requirements are aligned with WCAG 2.0 Level A and AA, making WCAG the technical foundation for Section 508 compliance. - European Accessibility Act (EAA)
WCAG is incorporated into EN 301 549, which organizations use to meet EAA accessibility requirements across the European Union.
Basically, organizations that must meet accessibility laws, deliver digital services to the public, or operate in regulated environments should follow WCAG guidelines as part of a structured approach to WCAG compliance.
Is WCAG a legal requirement?
WCAG itself is not a law. However, it is widely used as the standard for meeting digital accessibility requirements under many laws and regulations. In practice, organizations achieve WCAG compliance to demonstrate that their digital content meets legally enforceable accessibility requirements.
For example, WCAG is used to support compliance with laws such as the Americans with Disabilities Act (ADA), Section 508 in the United States, and the European Accessibility Act (EAA). In these cases, WCAG standards provide the technical framework for evaluating accessibility, even when the law does not explicitly name WCAG.
Because of this, many organizations treat WCAG compliance as a requirement when they are subject to accessibility regulations, involved in procurement, or delivering digital services to the public.
Benefits of WCAG compliance
Following WCAG standards does more than meet legal compliance. It helps organizations create digital experiences that are usable, consistent, and inclusive for a wider range of people in a wider set of usage environments. When accessibility is built into how digital products are designed and delivered, WCAG compliance becomes a driver of both usability and long-term value.
Deliver more accessible digital experiences
WCAG guidelines provide a clear framework for removing barriers and improving how users interact with digital content. This supports more consistent, usable experiences for people with disabilities, including those who rely on assistive technologies.
Reach more users and customers
Accessible digital experiences expand your audience. By meeting WCAG compliance requirements, organizations can serve users with a range of needs, including visual, auditory, cognitive, and mobility disabilities, as well as people using different devices or interacting with digital resources in different environments.
Improve usability for everyone
Many WCAG guidelines align with general usability best practices, such as clear navigation, readable content, and predictable interactions. This leads to better experiences for all users.
Support compliance and reduce risk
Because WCAG is used to help organizations meet legal accessibility requirements, achieving WCAG compliance helps organizations align with laws such as the ADA, Section 508, and the EAA, reducing legal and reputational risk.
Build a sustainable approach to accessibility
Organizations that adopt WCAG standards as part of their design, development, and content processes are better positioned to maintain accessibility over time, even as digital systems evolve.
At its core, WCAG compliance supports the goal of delivering digital experiences that are accessible to every person, everywhere.
What does WCAG compliance require?
Achieving WCAG compliance requires more than passing individual success criteria. It involves ensuring that digital content is accessible, usable, and compatible with assistive technologies across real-world scenarios. In practice, organizations meet WCAG compliance requirements by addressing three core areas.
Technical accessibility
WCAG compliance is based on meeting testable success criteria defined in WCAG guidelines, including success criteria for content appearance, structure, navigation, and interaction. These criteria provide a consistent, measurable foundation for building accessible websites, applications, and digital content.
Usability in real-world scenarios
Meeting technical requirements alone is not sufficient to ensure successful use. Digital experiences must support users in understanding content, navigating interfaces, and completing tasks independently. Accessibility must work in practice, not just in theory.
Assistive technology compatibility
Digital content must be compatible with assistive technologies such as screen readers, magnifiers, speech input, and keyboard operation. This ensures that users can interact with content regardless of how they access it.
Together, these elements define how organizations achieve and sustain WCAG compliance in a consistent and meaningful way.
How to achieve WCAG compliance
Achieving WCAG compliance requires a structured, ongoing approach that combines accessibility expertise, testing, and continuous improvement across digital systems.
Conduct an accessibility audit
Evaluate your websites, applications, and digital content against WCAG guidelines and success criteria to identify gaps and establish a baseline for WCAG compliance.
Remediate accessibility issues
Prioritize and address barriers identified in the audit, based on impact and effort to fix, focusing on issues that prevent users from accessing content or completing key tasks.
Validate conformance
Confirm that updates meet WCAG compliance requirements by verifying success criteria and ensuring consistent accessibility across user journeys.
Test with users
Conduct task-based usability testing with people with disabilities to verify that efforts to follow WCAG guidelines also ensure real-world usability for people.
Maintain accessibility over time
Integrate WCAG standards into design, development, and content workflows to sustain accessibility as digital experiences evolve.
Together, these steps help organizations move from one-time evaluation to a sustained accessibility practice.
WCAG compliance checklist
Most organizations start with these core steps to meet WCAG compliance requirements and establish a strong foundation for accessibility:
- Audit accessibility
Evaluate your websites, applications, and digital content against WCAG standards to identify gaps and establish a baseline for WCAG compliance. - Fix accessibility issues
Prioritize and remediate barriers that affect usability, focusing on issues that prevent users from accessing content or completing key tasks. - Test for accessibility
Validate improvements using automated tools and manual testing, including assistive technologies, to ensure alignment with WCAG guidelines. - Document conformance
Maintain clear documentation of how digital content meets WCAG compliance requirements, including how accessibility has been evaluated and implemented. - Monitor and maintain
Establish processes for ongoing testing, tracking, and improvement to sustain WCAG compliance over time.
This WCAG compliance checklist provides a starting point, but long-term success depends on integrating accessibility into how digital experiences are designed, developed, and maintained.
WCAG conformance vs. compliance
The terms WCAG conformance and WCAG compliance are often used interchangeably.
WCAG conformance is the technically accurate term. It refers to how well a website, application, or digital product meets the specific success criteria defined in WCAG standards. WCAG has a conformance framework that allows organizations to measure accessibility to evaluate whether digital content meets WCAG requirements at level A, AA, or AAA.
WCAG compliance is a commonly used term in business, legal, and procurement contexts. It generally refers to meeting WCAG requirements as part of broader organizational compliance efforts, though, correctly speaking, the term “compliance” should be used in reference to applicable accessibility laws.
Need help with WCAG compliance?
Understanding your current level of WCAG compliance is the first step toward delivering accessible, usable digital experiences. An accessibility audit can help identify gaps across your websites, applications, and content, while structured testing and validation support ongoing WCAG conformance.
If you’re evaluating your accessibility baseline or looking to strengthen WCAG conformance, Vispero’s Digital Accessibility Services experts can help through expert audits, assistive technology, testing, usability testing, and ongoing accessibility support.
WCAG FAQ
What is WCAG?
What does WCAG stand for?
What is WCAG compliance?
WCAG compliance refers to meeting the accessibility requirements, or success criteria, defined in WCAG. In practice, this means ensuring digital content is perceivable, operable, and understandable by people with disabilities, and compatible with assistive technologies across real-world scenarios.
Is WCAG legally required?
WCAG itself is a standard not a law, but it is widely used to help organizations meet applicable disability rights and accessibility laws. Laws such as the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and the European Accessibility Act (EAA), directly or indirectly reference WCAG standards as a means to evaluate accessibility of digital products and services.
What are WCAG standards?
WCAG standards is a term often used to refer to the collective set of guidelines and testable success criteria provided by WCAG that define how digital content should be presented, structured, and interacted with to support accessibility.