WCAG COMPLIANCE & CONFORMANCE

Meet WCAG with accessibility work that goes beyond a scan.

EqualAccess. finds the accessibility barriers affecting your website, fixes them at the code level, and verifies the improvements against WCAG.

Get automated and manual testing, assistive technology evaluation, remediation, retesting, and clear documentation—all from one accessibility team, with a scope agreed for your website.

  • Manual Testing
  • Code-Level Fixes
  • Assistive Technology
  • Verified Improvements

WCAG 2.2 · Levels A & AA · Websites & Web Applications
Specific legal or contractual targets are confirmed during scoping.

Visual demo of work performed by human experts, supported by testing tools. Illustrative findings and fixes; actual scope and results depend on the website.

THE TERMINOLOGY

“Compliance” and “conformance”
have different jobs.

You’ll often hear the terms used interchangeably. In a WCAG evaluation, the distinction helps keep technical findings and legal questions clear.

WCAG compliance

Common buyer language for efforts to meet WCAG accessibility requirements, often discussed alongside organizational policies, procurement, or legal obligations.

WCAG is a technical standard. Meeting it does not determine whether an organization has satisfied every law or regulation that may apply.

WCAG conformance

The term WCAG uses for satisfying its defined success criteria and conformance requirements at a claimed level.

A clean automated scan, or fixing most identified issues, does not establish conformance. The complete requirements and the scope of the claim matter.

The practical goal: understand what’s failing, fix the barriers, verify the result, and document the work accurately.

W3C guidance on understanding conformance.

THE STANDARD

Four principles.
One more accessible experience.

The Web Content Accessibility Guidelines are developed through W3C’s Web Accessibility Initiative. Their testable success criteria are organized around Perceivable, Operable, Understandable, and Robust.

Perceivable

Can people perceive the content?

Information should not depend on a single sense or presentation. Consider text alternatives, captions, adaptable structure, contrast, and content that remains usable when resized.

Alternative text · Captions · Contrast · Reflow · Structure

Operable

Can people operate the interface?

People should be able to navigate and use functionality without relying exclusively on a mouse. Keyboard access, focus, timing, pointer interactions, and navigation all matter.

Keyboard access · Focus · Navigation · Target size

Understandable

Can people understand what happens?

Content and controls should behave predictably. Clear instructions, helpful errors, consistent patterns, and accessible authentication help people understand and complete tasks.

Labels · Instructions · Errors · Predictable behavior

Robust

Can assistive technology understand it?

Content and controls need to expose useful information to browsers and assistive technologies. Semantic HTML and accurate names, roles, states, and values are central.

Semantic HTML · Names · Roles · States

Select a principle to highlight its example. The descriptions explain every principle without requiring interaction.

Read the W3C WCAG overview.

CONFORMANCE LEVELS

Three levels.
They build on one another.

Level AA includes Level A. Level AAA includes both A and AA, plus additional requirements. They describe cumulative conformance requirements, rather than quality scores.

For most EqualAccess. website engagements, Levels A and AA are the starting point unless a different target is required.

W3C does not recommend requiring AAA as a general policy for entire sites, because some content cannot satisfy every AAA criterion.

W3C guidance on conformance levels.

  1. A

    Foundational requirements

    The applicable Level A success criteria.

  2. AA

    A common evaluation target

    All Level A and AA success criteria, with the conformance requirements.

  3. AAA

    Additional requirements

    All Level A, AA, and AAA success criteria, with the conformance requirements.

WCAG VERSIONS

Which version should you use?

Begin with the requirements governing your project. WCAG 2.0, 2.1, and 2.2 remain existing standards; newer WCAG 2 versions add requirements rather than invalidating earlier versions.

WCAG 2.0

Established the core WCAG 2 framework and success criteria. It remains referenced in requirements including the Revised Section 508 Standards.

WCAG 2.1

Added criteria particularly relevant to mobile accessibility, low vision, and cognitive and learning disabilities. The DOJ’s Title II web and mobile rule uses 2.1 AA.

WCAG 2.2

Adds criteria for focus not being obscured, dragging, target size, consistent help, redundant entry, and accessible authentication.

W3C encourages the latest version

Free to choose? WCAG 2.2 is a strong target for new work. If a law, contract, procurement requirement, or customer specifies a version and level, test against that required target and document the mapping.

WCAG 2 versions are designed for backward compatibility. One specific change is the removal of obsolete 4.1.1 Parsing in 2.2; W3C explains related 2.0 errata and 2.1 notes. Version guidance · What’s new in 2.2 · Section 508 baseline · DOJ Title II baseline. Sources reviewed October 4, 2026.

BEYOND INDIVIDUAL CHECKS

Conformance is more than
an isolated checklist.

WCAG defines five conformance requirements. Individual success criteria matter, but they are not the whole picture.

  1. Requirement 1

    Selected level

    For AA, satisfy the applicable Level A and AA success criteria and the conformance requirements.

  2. Requirement 2

    Complete pages

    Conformance applies to a full page, including responsive variations—not just the parts that pass.

  3. Requirement 3

    Complete processes

    Evaluate all steps in a multi-page process. An accessible product page does not establish an accessible checkout.

  4. Requirement 4

    Accessibility support

    Rely on technology used in ways that work with users’ browsers and assistive technologies.

  5. Requirement 5

    No interference

    Content not relied upon for conformance must still avoid blocking access to the rest of the experience.

ILLUSTRATIVE PURCHASING JOURNEY
  1. Product
  2. Cart
  3. Address
  4. PaymentKeyboard barrier
  5. Confirmation

A barrier at payment can prevent a customer completing the purchase. That is why EqualAccess. tests experiences, not just individual URLs.

Read the five W3C conformance requirements.

HUMAN TESTING MATTERS

Automated testing finds issues.
It doesn’t tell the whole story.

Tools can quickly identify detectable problems and help monitor large websites. Other requirements depend on human judgment, context, interaction, and assistive technology behavior.

AUTOMATED

Find repeatable technical issues.

  • Certain contrast failures
  • Missing attributes
  • Some structural issues
  • Certain ARIA problems
  • Repeatable technical patterns
MANUAL

Evaluate how the experience works.

  • Meaningful alternative text
  • Logical focus order
  • Keyboard usability
  • Forms and error handling
  • Names in context and complete journeys
ASSISTIVE TECHNOLOGY

Check important interactions.

  • Screen reader output
  • Component announcements
  • Form behavior
  • Dynamic updates
  • Navigation and dialogs
A clearer, evidence-based picture of accessibility.
Explore Accessibility Audits & Testing

W3C recognizes machine evaluation, human evaluation, or a combination of both in testing success criteria. Read W3C conformance guidance.

THE EVALUATION

We test how people
use your website.

Agree the WCAG version, conformance level, representative pages, technologies, and important journeys before testing begins.

Website + component + journey
An experience to evaluate.
NavigationContentFormsDialogsMedia
Account emailVisible label + meaningful name
Page structure
Interaction behavior
Assistive technology output
Complete user journey
Illustrative evaluation map. Coverage and testing methods are defined for each engagement.
  • 01

    Content & Structure

    Headings, landmarks, lists, tables, language, images, text alternatives, and semantic relationships.

  • 02

    Keyboard Access

    Tab order, operation, focus movement, traps, shortcuts, and interaction without a mouse.

  • 03

    Focus & Navigation

    Focus visibility, menus, skip mechanisms, page titles, link purpose, and navigation patterns.

  • 04

    Forms & Errors

    Labels, instructions, required fields, validation, error identification, status messages, and correction assistance.

  • 05

    Interactive Components

    Menus, tabs, dialogs, accordions, carousels, tooltips, filters, and custom controls.

  • 06

    Visual Presentation

    Contrast, zoom, text spacing, reflow, orientation, hover/focus content, and visual states.

  • 07

    Media

    Captions, transcripts, audio description requirements, controls, and alternatives where applicable.

  • 08

    Assistive Technology

    Names, roles, states, dynamic updates, reading order, and screen reader interaction.

  • 09

    User Journeys

    Search, registration, login, account management, booking, form submission, and checkout.

FROM FINDINGS TO VERIFIED IMPROVEMENTS

We don’t stop at telling you
what’s wrong.

One consistent five-step process connects a clear evaluation target to practical remediation and an accurate record of the work.

01 · Assess

Define what needs to be evaluated.

Identify important pages, templates, components, journeys, technologies, and the WCAG version and level. Agree responsibilities and a representative scope.

OUTPUTTesting scope

Scope register
  • TargetWCAG 2.2 AA
  • Pages & templatesAgreed sample
  • JourneysComplete tasks
Illustrative project detail · human-led work

02 · Manual Testing

Find barriers. Set clear priorities.

Combine automated analysis with expert keyboard, manual, and assistive technology testing. Organize findings by criterion, user impact, recurrence, and remediation needs.

OUTPUTVerified findings + remediation priorities

Findings register
  • Keyboard operationInvestigate
  • Error associationReproduced
  • Remediation orderPrioritized
Illustrative project detail · human-led work

03 · Code-Level Remediation

Fix the underlying implementation.

Correct scoped issues in HTML, CSS, JavaScript, themes, templates, content, and components. We can implement changes or work with your developers and agency.

OUTPUTCode-level improvements

Form relationship · example
<input id="email"
  aria-invalid="true"
  aria-describedby="email-error">

<p id="email-error">
  Enter a valid email address.
</p>
Illustrative project detail · human-led work

04 · Retest & Verify

Repeat the task after the change.

Retest remediated functionality using appropriate manual, keyboard, assistive-technology, and automated checks. Record whether the fix works in the tested environment.

OUTPUTVerification results

Retest record
  • Keyboard journeyRetested
  • Error announcementVerified
  • Remaining issuesRecorded
Illustrative project detail · human-led work

05 · Documentation

Create a clear technical record.

Document what was evaluated, the barriers found, remediation status, test evidence, and remaining limitations. Scope formal product reporting separately when needed.

OUTPUTAccessibility documentation

Project evidence
  • Scope & findingsIncluded
  • Fixes & retestsLinked
  • Known limitationsDocumented
Illustrative project detail · human-led work

Stages and deliverables depend on the engagement. An audit-only project does not automatically include implementation or a conformance claim. All examples above are illustrative.

WHAT REMEDIATION ACTUALLY LOOKS LIKE

From WCAG finding
to verified fix.

Explore four illustrative issues. Each example connects a barrier to its impact, a technical correction, and the work needed to verify it.

Keyboard accessibility example

BEFORE · FINDING

Choose a delivery option

A dropdown works with a mouse but cannot be fully operated with a keyboard.

Mouse works · keyboard path blocked

Accessibility impact
A keyboard user may be unable to choose an option or finish the task.

CODE-LEVEL FIX

Correct keyboard behavior, focus management, semantics, and state communication.

Native <select>, where suitable Or implement the appropriate ARIA pattern + key behavior + accurate states.
VERIFIED · RETEST

Options can be reached and selected.

Retest keyboard operation, focus behavior, and relevant screen reader output.

Remediated and retested

Illustrative result for this issue, not a claim about a complete website.

Forms accessibility example

BEFORE · FINDING

Email address

An error is visible but not programmatically associated with its field.

Visible error · missing relationship

Accessibility impact
A screen reader user may not know which field needs correction or why.

CODE-LEVEL FIX

Associate the error with the field and update invalid state and feedback appropriately.

<input id="email" aria-invalid="true" aria-describedby="email-error"> <p id="email-error"> Enter a valid email. </p>
VERIFIED · RETEST

Field and error are connected.

Submit again and check that the field, error, and correction path are communicated.

Remediated and retested

Illustrative result for this issue, not a claim about a complete website.

Contrast accessibility example

BEFORE · FINDING

Important account information

Important normal-sized text falls below the applicable contrast threshold.

Contrast needs correction

Accessibility impact
People with low vision may have difficulty reading the information.

CODE-LEVEL FIX

Adjust foreground or background colors while preserving the intended hierarchy.

/* Example of an accessible pair */ color: #10213A; background: #FFFFFF; /* Check affected states too. */
VERIFIED · RETEST

Color pair and affected states retested.

Recalculate the ratio and inspect relevant states, including hover and focus.

Remediated and retested

Illustrative result for this issue, not a claim about a complete website.

Dialog accessibility example

BEFORE · FINDING

Delivery preferences

A modal opens, but focus stays behind it and its purpose is not announced.

Dialog purpose and focus unclear

Accessibility impact
Users may interact with the page behind the dialog or miss the dialog content.

CODE-LEVEL FIX

Correct naming, semantics, initial focus, focus containment, and focus return.

<dialog aria-labelledby="title"> <h2 id="title"> Delivery preferences </h2> <!-- controls and close action --> </dialog>
VERIFIED · RETEST

Dialog purpose and focus behavior retested.

Retest with keyboard and relevant assistive technology, including closing the dialog.

Remediated and retested

Illustrative result for this issue, not a claim about a complete website.

Illustrative examples and code excerpts, not complete implementations. Actual findings, tests, and remediation depend on the website and applicable criteria.

DELIVERABLES

Clear findings.
Real fixes. Verified improvements.

The exact deliverables are agreed with your team. Each should make the next action easier to understand.

Website accessibility
evaluation record
Scope · Findings · Remediation · Verification
Evaluation target
WCAG version + level
Testing coverage
Defined
Retest evidence
Issue-linked
Limitations
Explicit
Illustrative report structure. An ACR can be separately scoped for product or procurement needs.
Explore VPAT & ACR reporting
  • WCAG Accessibility Assessment

    Evaluation against the agreed version and level, using an appropriate combination of automated and manual testing.

  • Manual Expert Testing

    Human review of important pages, components, interactions, and journeys that tools cannot meaningfully evaluate alone.

  • Assistive Technology Testing

    Screen reader and keyboard evaluation where appropriate, with the testing environment documented.

  • Code-Level Remediation

    Technical correction of barriers in the website when implementation is included in scope.

  • Verification & Retesting

    Relevant fixes retested to confirm that the corrected experience behaves as intended.

  • Accessibility Documentation

    Clear records of scope, findings, remediation status, verification, and known limitations.

STANDARDS & REQUIREMENTS

WCAG is a technical standard.
Legal requirements can reference it.

Laws, regulations, procurement requirements, contracts, and organizational policies can specify particular WCAG versions or levels. Legal scope and technical evaluation are related questions, not the same determination.

WCAGTechnical accessibility standard

ADA Title II

The DOJ’s rule for covered state and local government web content and mobile apps uses WCAG 2.1 Level AA, subject to its scope and exceptions.

Explore ADA Title II Compliance

Section 508

The Revised Section 508 Standards incorporate WCAG 2.0 Level A and AA for covered federal ICT, alongside other applicable Section 508 requirements.

Explore Section 508 Compliance

Other requirements

Private-sector teams may encounter WCAG through customers, procurement, contracts, internal policies, or legal accessibility considerations.

Explore ADA Website Compliance

Official references: DOJ Title II guidance · Section508.gov applicability and conformance.

ACCURATE CLAIMS MATTER

A 95% score is not
WCAG conformance.

Scores, issue counts, and health indicators can help track progress. They are not conformance levels.

A conformance claim depends on the applicable success criteria, all conformance requirements, and the defined scope and level. It does not follow from reaching a scanner score.

EqualAccess. separates progress metrics from claims about what has been evaluated and established.

W3C guidance on conformance claims.

An illustrative 95% scanner score does not establish Level AA conformance. Applicable criteria, complete requirements, and testing evidence determine the claim.

ACCESSIBILITY OVER TIME

A website can change
after you’ve tested it.

Content, themes, plugins, third-party applications, design systems, and new code can introduce barriers after remediation. Build accessibility into website maintenance.

  1. AFTER TESTING

    A documented baseline

    Record the evaluated state and remaining limitations.

  2. NEXT RELEASE

    New components

    Review changes before they reach users.

  3. CONTENT UPDATE

    New pages & media

    Check structure, alternatives, and media access.

  4. THIRD-PARTY CHANGE

    Updated integrations

    Revisit the user journey and vendor dependencies.

  5. ONGOING

    Monitor, test & fix

    Combine regular checks with manual review and support.

Keep accessibility from drifting.

Monitoring helps surface changes; periodic manual review and remediation remain important.

Explore Ongoing Monitoring & Support

PRACTICAL ACCESSIBILITY SUPPORT

For teams that need
more than another report.

  • You received an accessibility report

    You know there are problems and need help understanding, prioritizing, and fixing them.

    Explore Code-Level Remediation
  • You’re preparing for procurement

    A customer or procurement team wants evidence that accessibility has been evaluated.

    Explore VPAT & ACR
  • You’re redesigning or rebuilding

    Test accessibility before barriers become embedded in the new experience.

  • You’re responding to a claim

    Your legal team needs technical accessibility work performed on the website.

    Get Priority Support
  • You want to know where you stand

    Define an accessibility target and get a credible evaluation of the current experience.

  • Your website was remediated before

    The site has changed and you need to investigate new or recurring barriers.

Not sure where to begin?

Get a Free Review

WCAG FAQ

Common questions.
Clearer answers.

About the standard, testing, remediation, and the claims you make.

W3C overview.

W3C conformance guidance.

WCAG stands for Web Content Accessibility Guidelines. It is an international accessibility standard developed through W3C’s Web Accessibility Initiative, with testable success criteria intended to make web content more accessible to people with disabilities.

“WCAG compliance” is common language for meeting WCAG accessibility requirements. “Conformance” is the terminology WCAG uses for satisfying its defined success criteria and conformance requirements at a particular level.

WCAG 2.2 Level AA conformance requires the applicable Level A and AA success criteria, along with the conformance requirements. Level AA includes Level A; it is not a separate set of checks that can establish conformance independently.

W3C encourages the latest version when organizations are free to choose, making WCAG 2.2 a strong target for new work. However, laws, contracts, procurement requirements, or customer requests may specify WCAG 2.1 or 2.0. Confirm the required version and level before testing.

Not by itself. Tools can identify many detectable issues, but some requirements depend on human evaluation, context, interaction testing, and assistive technology behavior. EqualAccess. combines automated analysis with expert manual evaluation.

No. A clean automated scan indicates that the tool did not detect the issues it is designed to identify. It does not establish that every applicable success criterion and conformance requirement has been satisfied.

Yes. When remediation is included in scope, we can address barriers in HTML, CSS, JavaScript, themes, templates, forms, navigation, and interactive components, followed by verification and retesting.

That depends on the requirements governing your project. W3C does not recommend requiring Level AAA conformance as a general policy for entire websites, because some content cannot satisfy every AAA success criterion.

No. Technical accessibility work can address barriers and provide useful evidence, but EqualAccess. does not represent conformance as a guarantee against legal claims. Discuss legal questions with qualified counsel.

There is no single interval for every website. Testing should reflect how often the site changes, the importance of its journeys, and your accessibility requirements. Redesigns, new components, integrations, and significant releases are important times to retest.

START WITH YOUR WEBSITE

Find the barriers. Fix the code.
Verify the experience.

Whether you’re working toward WCAG conformance, responding to an accessibility requirement, or making your website easier to use, begin by understanding what’s happening on the site.

An existing accessibility report, audit, demand letter, or procurement requirement can help define the technical issues and scope for your review.

Opens in a new tab.