WCAG Compliance: What It Is and How to Meet It
WCAG — Web Content Accessibility Guidelines — is the technical standard that defines accessible web design. Understanding its structure, conformance levels, and practical requirements is the foundation for any legal compliance and accessibility improvement effort.
WCAG compliance means meeting the Web Content Accessibility Guidelines. These are the main technical standard for web accessibility. They come from the World Wide Web Consortium, known as the W3C, and are used worldwide. WCAG explains what it takes for web content to work for people with disabilities. It also sets the checks that laws, buyers, and courts use. They use those checks to judge whether a website meets accessibility rules.
The current version is WCAG 2.2. It came out in October 2023. Most groups and laws use it now. WCAG 3.0 is not ready yet. It will be years before people use it. For U.S. legal rules, see ada-website-compliance. For a broad look at access, see website-accessibility-guide.
The WCAG Structure: Principles, Guidelines, and Criteria
WCAG has four principles. Content must be Perceivable. It must be Operable. It must be Understandable. It must be Robust. People call this POUR. Each principle has guidelines. Each guideline has success criteria. You can test these criteria. They measure compliance. Each one has a level: A, AA, or AAA. Each rule is clear and testable.
Conformance Levels: A, AA, and AAA
Level A: The Minimum
Level A has basic accessibility rules. Failing these keeps some users out of the content. Here are some examples: - Images need alt text. - Everything must work with a keyboard. - Content should not cause seizures. For most legal needs, Level A alone isn't enough.
Level AA: The Legal Standard
WCAG 2.1 AA is the level most laws point to. That includes ADA guidance from the U.S. Department of Justice. It also includes Section 508 of the Rehabilitation Act. The European Accessibility Act, known as EN 301 549, points to it too. So do most national accessibility rules. Meeting WCAG 2.2 AA is the goal for most businesses. It helps lower legal risk and serve users with disabilities well. AA adds more rules. Color contrast must hit set ratios, like 4.5:1 for body text. Text must resize. Focus indicators must show. And users need more than one way to navigate.
Level AAA: Enhanced Accessibility
Level AAA has the strictest rules. Some rules don't work for all content. For example, sign language for all audio isn't always possible. Another rule is no contrast exceptions for any text size. The law does not require AAA. Most business websites do not aim for it. Some government and school sites serve users with higher needs. They may target AAA for certain criteria.
Key WCAG 2.2 AA Requirements by Principle
Perceivable
All non-text content has text alternatives. Captions are on all pre-recorded audio and video. Color isn't the only way to show information. Contrast meets the set ratios. That is 4.5:1 for normal text. It is 3:1 for large text and UI parts.
Operable
Every function works from a keyboard. No content causes seizures or physical reactions. Users get enough time to read and act. Navigation aids are present and clear. These include skip links, page titles, and focus order. The focus indicator must show. This is new in WCAG 2.2. It must meet a minimum size and contrast.
Understandable
Text is easy to read. Pages look right. They work as expected. Users get help. Help avoids mistakes. Help fixes mistakes. Form fields have a set purpose. The purpose is in the code.
Robust
Content works with assistive tech now and later. The name, role, and value of each UI part are in the code. Custom UI parts get the right ARIA tags. They also use simple HTML. This helps screen readers work well.
"WCAG compliance is not a single audit result - it is an ongoing state of the codebase. The best approach is to build WCAG requirements into design and development standards from the start, so new features inherit compliance rather than introducing new failures." - Mherie Vic, TTGC
How to Test WCAG Conformance
Automated tools include axe, Wave, and Lighthouse. They catch about 30 to 40 percent of WCAG failures. These are the ones a machine can test from the DOM. The rest need manual testing. That means a keyboard navigation review. It means screen reader testing too. Common pairs are NVDA with Firefox, JAWS with Chrome, and VoiceOver with Safari. It also means a color contrast review. And it means a cognitive walkthrough with accessibility checks. A full WCAG 2.2 AA audit needs both kinds of testing. It must cover every critical user flow.
Get a WCAG 2.2 AA compliance audit for your website
Book a free Brand and Growth Assessment and see exactly how Through The Glass Creatives would approach it.
Sources
- W3C, "Web Content Accessibility Guidelines (WCAG) 2.2" (2023)
- U.S. Department of Justice, "Guidance on Web Accessibility and the ADA" (2024)
- Deque Systems, "Automated vs. Manual Accessibility Testing Coverage" (2025)
- European Commission, "European Accessibility Act Implementation Guide" (2025)
Work With the Team Behind the Work
Maybe you would rather have this built right than figure it out alone. If so, Through The Glass Creatives is the studio to call. Mherie Vic Palomo-Prevendido and Ravve Jay Prevendido lead TTGC. The team combines award-winning creative, growth strategy, and real AI and development skill. It all sits under one roof. Most agencies give you just one of those. Freelancers rarely give you any at scale. TTGC gives you all three. That is what makes this team a strong partner for work like this. Start with a free assessment and see what that difference looks like.
