If your compliance documentation still cites WCAG 2.0 Level AA as the federal accessibility standard your product meets, you are technically correct. You may also be building toward a baseline that is one signature away from being out of date. A bill sitting in Congress would raise that baseline to WCAG 2.2 AA, add cloud services and AI-driven interfaces to what counts as covered technology, and tighten what contracting officers can accept as proof of compliance. It has not passed. But the agency that runs federal procurement isn't waiting around to find out if it will.
For federal contractors, that combination — a pending legal shift plus an agency already acting on the spirit of it — is the part worth paying attention to, regardless of when or whether the bill clears both chambers.
What the Section 508 Refresh Act Would Actually Change
The Section 508 Refresh Act was introduced in Congress in July 2024. Its core proposal is straightforward: move the technical baseline for federal information and communications technology (ICT) accessibility from WCAG 2.0 Level AA — the standard written into Section 508 regulations for over a decade — up to WCAG 2.2 Level AA, the current version of the guidelines. Alongside that update, the bill would expand what falls under Section 508's scope to explicitly include cloud services and AI-driven interfaces, and it would strengthen the documentation contractors must produce during procurement to demonstrate conformance.
The Stat: The bill proposed moving the federal ICT accessibility baseline from WCAG 2.0 Level AA to WCAG 2.2 Level AA and extending coverage to cloud services and AI-driven interfaces. (Source: Section 508 Refresh Act, introduced July 2024)
The jump from WCAG 2.0 to 2.2 is not cosmetic. WCAG 2.2 adds success criteria covering things like target size for interactive elements, consistent help mechanisms, and clearer authentication flows — areas that didn't exist as formal requirements under the 2.0 baseline many federal systems were built and tested against. Combine that with explicit language covering cloud services and AI-driven interfaces, and a meaningful share of modern federal ICT — SaaS procurement, chatbots, AI-assisted case management tools — would move from a gray area into direct scope.
As of March 2026, the Section 508 Refresh Act had not been enacted into law. It remains a proposal moving through the legislative process, not a binding requirement. That distinction matters for contract language and legal exposure today. It matters less for planning purposes, because the agency responsible for federal procurement standards is already moving in the same direction.
GSA Isn't Waiting on Congress
While the bill sits in the legislative pipeline, the General Services Administration has been building out the infrastructure to enforce a stricter accessibility standard regardless of when — or whether — the Refresh Act becomes law.
GSA's Fiscal Year 2025 Governmentwide Section 508 Assessment, published around March 2026 and prepared in coordination with the Office of Management and Budget and the U.S. Access Board, highlighted new AI-enabled capabilities added to GSA's Solicitation Review Tool (SRT). The assessment also described deeper integration between the SRT and GSA's Accessibility Requirements Tool, aimed at producing more consistent Section 508 requirements language across federal procurements agency-wide.
Read together, the legislative and operational tracks tell a consistent story: the bar for accessibility in federal contracting is rising, whether through statute or through the tools contracting officers use every day to write and review solicitations. A contractor whose accessibility documentation is built to satisfy the letter of WCAG 2.0 today has no guarantee that documentation will satisfy the review tools evaluating next year's bid.
Two Baselines, Side by Side
| Current Section 508 Baseline | Proposed Under Refresh Act | |
|---|---|---|
| Technical standard | WCAG 2.0 Level AA | WCAG 2.2 Level AA |
| Scope | Traditional ICT | Traditional ICT + cloud services + AI-driven interfaces |
| Documentation requirements | Existing Section 508 conformance reporting | Strengthened procurement documentation requirements |
| Legislative status (as of March 2026) | In force | Introduced July 2024; not yet enacted |
| Related agency activity | — | GSA FY2025 assessment: AI-enabled SRT capabilities, deeper Accessibility Requirements Tool integration |
Neither track moves in isolation. A bill can stall in committee for years without dying, and an agency assessment can quietly reshape what "acceptable" documentation looks like long before any statute changes. Federal contractors who treat the Refresh Act as the only signal worth watching risk missing the more immediate shift already happening inside GSA's own review process — the one shaping how your next solicitation response gets evaluated.
What This Means for Contractors Right Now
None of this requires contractors to wait for a floor vote before acting. A few things are true independent of the bill's outcome:
- WCAG 2.2 AA is already the more defensible target. It is the current version of the guidelines referenced by accessibility professionals and increasingly by agency reviewers, whether or not it is yet the codified legal minimum for Section 508.
- Cloud and AI tooling is where the gap usually lives. If your accessibility testing program was built around traditional web pages and desktop software, cloud-delivered SaaS components and AI-driven interfaces are the areas most likely to have never been formally assessed.
- Documentation quality is becoming a review criterion, not a formality. GSA's own tooling changes point toward more rigorous, more consistent evaluation of the conformance documentation contractors submit — not just the underlying product.
The scale of the underlying problem is also worth keeping in view. Across the web broadly, WebAIM's Million study has found that roughly 95.9% of home pages have detectable WCAG 2 failures — a reminder that "we tested it once" and "it conforms today" are not the same claim. And the population affected is not a rounding error: the CDC estimates that roughly 1 in 4 US adults have a disability, and the World Health Organization estimates that about 8.3% of men and 0.5% of women have some form of color vision deficiency — a single, common condition that alone can break interfaces never tested for color contrast and reliance on color alone.
For a federal contractor, that combination of rising legislative pressure, tightening agency review tooling, and a genuinely large affected user population is not a reason to panic. It is a reason to know exactly where your current ICT stands against WCAG 2.2 AA before a solicitation review — or a change in law — forces the question.
Get Ahead of the Baseline, Not Behind It
Waiting for the Section 508 Refresh Act to become law before addressing WCAG 2.2 gaps means waiting to react to a standard that GSA's own review tools are already being built to expect. The more defensible position is knowing today, in specific and documented terms, where your ICT stands against WCAG 2.2 AA, where cloud and AI-driven components fall outside current testing coverage, and what a stronger conformance documentation package would need to include.
If you manage accessibility compliance for federal contracts, now is the time to close that gap before it becomes a procurement liability. Get a full accessibility audit from WCAG.World to see exactly where your systems stand against WCAG 2.2 AA and what a Section 508 Refresh Act-ready documentation package looks like.