San Antonio, TX · Military City, USA UEI L58JZMKRCLM5  ·  CAGE 203C1  ·  NAICS 541511  ·  SAM.gov Active
OVERVIEW

If a solicitation says your website, app, or document must be “508 compliant” or “accessible,” what it almost always means in practice is WCAG 2.1 Level AA. WCAG — the Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C) — is the technical rulebook for building digital content people with disabilities can actually use. This is a plain-English walkthrough of what WCAG 2.1 AA requires, how its conformance levels work, and why AA (not A, not AAA) is the line nearly every federal and state contract draws. We bid federal and state IT work every week, and accessibility language shows up constantly — so this is the explainer we wish more vendors read first. This is educational, not legal advice: verify the exact standard against your specific solicitation and the Section 508 requirements that apply.

WHAT IT IS

WCAG, POUR, and why “AA” is the number that matters

Start with the structure — it makes every requirement easier to read.

WCAG is maintained by the W3C, the international standards body for the web. WCAG 2.1 — published as a W3C Recommendation in 2018 — organizes every requirement under four foundational principles, known by the acronym POUR.

P

Perceivable

Users must be able to perceive the information — through sight, sound, or touch. This covers text alternatives for images, captions for video, and sufficient color contrast so text is legible.

O

Operable

The interface must be operable by everyone, not just mouse users. Everything must work by keyboard, focus must be visible, and users need enough time and control to complete tasks.

U

Understandable

Content and operation must be understandable — readable text, predictable behavior, clear labels and instructions, and helpful error messages when something goes wrong.

R

Robust

Content must be robust enough to work reliably with assistive technologies like screen readers — which means valid, well-structured code that tools can parse correctly.

Why AA, specifically? WCAG defines three conformance levels. Level A is the bare minimum — meeting it alone still leaves major barriers. Level AAA is the highest bar, but the W3C itself notes it is not recommended as a blanket requirement for entire sites because some content cannot meet every AAA criterion. Level AA sits in the practical middle, and that is exactly why laws, policies, and procurement language converge on it.

THE LEVELS

A vs. AA vs. AAA — what conformance actually means

The levels stack: AA includes all of A, and AAA includes all of A and AA.

LevelWhat it isWhere you see it
AMinimum conformance. Removes the most fundamental barriers, but not enough on its own.Rarely the contract target — usually a floor, not a goal.
AAIncludes all Level A criteria plus the AA set. The widely accepted compliance standard.Section 508, most state laws, and the typical solicitation requirement.
AAAHighest level. Includes A and AA plus stricter criteria. Not advised as a site-wide mandate.Targeted enhancements; specialized contexts.

To claim AA conformance, a page must satisfy every applicable Level A and Level AA success criterion — you do not get to pick and choose. There is no partial “mostly AA.” WCAG 2.1 added 17 new success criteria on top of WCAG 2.0, broadening coverage for mobile devices, low-vision users, and cognitive and learning disabilities. Of those 17, seven are at Level AA — including Reflow, Non-Text Contrast, Text Spacing, and Status Messages.

Counts evolve across WCAG versions (2.0, 2.1, 2.2). If a contract requires an exact criteria count or a specific version, confirm it against the official spec at w3.org/TR/WCAG21 rather than a third-party summary.

THE CRITERIA

Important AA success criteria, in plain terms

A representative sample — not the full list — of what AA conformance demands.

Color contrast (1.4.3)

Normal text needs a contrast ratio of at least 4.5:1 against its background; large text needs 3:1. Low-contrast gray-on-white fails this constantly.

Keyboard accessible (2.1.1)

Every function must work using only a keyboard — no mouse-only menus, drag-and-drop traps, or hover-only controls that lock out non-mouse users.

Focus visible (2.4.7)

When a user tabs through a page, the element in focus must show a visible indicator. Removing the focus outline in CSS is a common, avoidable failure.

Resize text (1.4.4)

Text must scale up to 200% without loss of content or function — no clipped, overlapping, or disappearing text when a user zooms in.

Labels & instructions (3.3.2)

Form inputs need clear, programmatically associated labels so screen-reader users know what each field expects.

Reflow & spacing (2.1 adds)

New in 2.1: content must reflow to a narrow viewport without horizontal scrolling, and remain readable when users adjust text spacing.

An automated scanner is a floor, not a certification. Tools reliably catch contrast and missing-label issues, but they cannot judge whether alt text is meaningful, whether focus order is logical, or whether a custom widget is truly operable. Real AA conformance pairs automated checks with manual and assistive-technology testing. Run a quick first pass with our accessibility checker, then plan for human review.

THE 508 LINK

How WCAG 2.1 AA relates to Section 508

Two different things that get used as if they were the same.

Section 508 of the Rehabilitation Act is U.S. law requiring federal agencies’ information and communication technology to be accessible. WCAG is the technical standard that defines what “accessible” means in measurable terms. The two connect by reference: the U.S. Access Board’s Revised 508 Standards (effective January 2018) incorporate the W3C’s WCAG Level A and Level AA success criteria by reference for web content. In short — 508 is the legal obligation; WCAG AA is the yardstick it points to.

For federal contracts

If you build or deliver digital ICT to a federal agency, expect AA conformance and an Accessibility Conformance Report (often a VPAT) in the deliverables. Read the exact WCAG version the solicitation cites.

For state & commercial work

Many states and private accessibility expectations also default to WCAG 2.1 AA. The principle is the same: AA is the practical compliance line nationwide and overseas alike.

This is educational, not legal advice. The Access Board updates standards over time and individual solicitations vary — verify the governing version and scope against the U.S. Access Board ICT standards, Section508.gov, and your specific contract. Need a deeper read on the law? See our Section 508 compliance guide.

COMMON QUESTIONS

Questions, answered

Is WCAG 2.1 AA a legal requirement?
WCAG itself is a technical standard, not a law. But it becomes legally binding by reference. For U.S. federal information and communication technology, Section 508 of the Rehabilitation Act incorporates WCAG Level A and AA success criteria for web content. Many state laws and accessibility policies also point to WCAG 2.1 AA. Always verify the exact version and scope against your specific solicitation or jurisdiction — this is educational, not legal advice.
What is the difference between Level A, AA, and AAA?
They are stacking conformance levels. Level A is the minimum and removes only the most basic barriers. Level AA includes everything in A plus additional criteria, and is the standard most laws and contracts require. Level AAA is the strictest and includes A and AA plus more — but the W3C does not recommend AAA as a blanket requirement for entire sites because some content cannot meet every AAA criterion.
What does the 4.5:1 contrast ratio mean?
It is the minimum color contrast WCAG AA requires between normal-size text and its background, so the text stays legible for people with low vision or color deficiencies. Large text (roughly 18pt, or 14pt bold) has a lower 3:1 minimum. Low-contrast light-gray text on a white background is one of the most common AA failures and is easy to catch with an automated check.
What is the difference between WCAG and Section 508?
Section 508 is U.S. law requiring federal agencies’ digital technology to be accessible. WCAG is the technical standard, published by the W3C, that defines what accessible actually means in testable criteria. They connect because the Revised Section 508 Standards incorporate WCAG Level A and AA success criteria by reference for web content. So 508 is the legal obligation and WCAG AA is the measurable yardstick it uses.
Does an automated accessibility scan prove AA conformance?
No. Automated tools are a useful first pass and reliably catch issues like low contrast and missing form labels, but they cannot confirm full AA conformance. They cannot judge whether alt text is meaningful, whether keyboard focus order is logical, or whether a custom component is genuinely operable with a screen reader. Treat an automated check as a floor, then add manual and assistive-technology testing.
What did WCAG 2.1 add compared to WCAG 2.0?
WCAG 2.1, published by the W3C in 2018, added 17 new success criteria on top of WCAG 2.0 to better cover mobile devices, users with low vision, and people with cognitive or learning disabilities. Seven of those are at Level AA, including Reflow, Non-Text Contrast, Text Spacing, and Status Messages. WCAG 2.1 keeps all of WCAG 2.0’s criteria, so it is backward compatible.
BUILD IT ACCESSIBLE FROM THE START

Make WCAG 2.1 AA a deliverable, not a scramble

BrandShyp builds and remediates IT and software to WCAG 2.1 AA / Section 508 for government and commercial clients nationwide and overseas — let’s scope your accessibility work before the deadline does.