2026-05-17 · 5 min read

Section 508 vs WCAG 2.1: Which Standard Actually Applies to Your Government Website?

# Section 508 vs WCAG 2.1: Which Standard Actually Applies to Your Government Website?

The question comes up consistently in conversations with state and local government IT directors: "We've addressed Section 508 — does that count for Title II compliance?"

The short answer is no, and the distinction matters enough to affect your compliance strategy heading into April 2027.

What Section 508 is and who it applies to

Section 508 of the Rehabilitation Act is a federal law. It requires federal agencies — departments, agencies, and offices of the federal government — and organizations that receive federal funding to ensure their information and communications technology is accessible to people with disabilities. The Access Board issues the technical standards that define what "accessible" means under Section 508.

The most recent revision of the 508 standards, issued in 2018, incorporates WCAG 2.0 Level A and AA by reference. Not WCAG 2.1. WCAG 2.0. This is an important distinction that becomes relevant below.

Section 508 also applies to federal contractors that develop or provide ICT to federal agencies. If a vendor is building a website for the federal government, 508 applies to that vendor's work product.

What Section 508 does NOT do is impose direct requirements on state and local government websites as a category. Florida counties, municipalities, school districts, transit authorities, water management districts, and other state and local entities are not federal agencies. Their websites are not subject to Section 508 simply by virtue of being government websites.

What Title II of the ADA actually requires

Title II of the Americans with Disabilities Act prohibits discrimination on the basis of disability by state and local government entities. The DOJ has authority to issue regulations implementing Title II, and the DOJ Title II Final Rule — published in April 2024 and subsequently amended to extend the compliance deadline — creates specific, binding technical requirements for state and local government websites.

The rule requires conformance to WCAG 2.1 Level AA. Not WCAG 2.0. Not Section 508. WCAG 2.1 Level AA, specifically.

The compliance deadline for jurisdictions with a population of 50,000 or more is April 26, 2027.

How the two standards differ in practice

Since Section 508 references WCAG 2.0 and the Title II rule requires WCAG 2.1, there is a version gap between the two frameworks. WCAG 2.1 added 17 new success criteria to the original 50 in WCAG 2.0. The most significant additions for government sites include:

1.3.4 Orientation — Content cannot be locked to a specific display orientation. Government sites that force landscape view on mobile fail this criterion.

1.3.5 Identify Input Purpose — Form fields collecting personal data (name, address, phone, email) must include the appropriate HTML autocomplete attribute. Many government forms do not.

1.4.10 Reflow — Content must be usable at 400% zoom without requiring horizontal scrolling. This affects most government sites that were not designed with reflow in mind.

1.4.11 Non-text Contrast — UI components (buttons, input borders, focus indicators) and informational graphics must meet a 3:1 contrast ratio against adjacent colors. This differs from 1.4.3, which covers text contrast.

1.4.12 Text Spacing — No loss of content or functionality when letter-spacing, line-height, word-spacing, and paragraph spacing are all increased. This is commonly failed by government sites with tightly laid out content areas.

1.4.13 Content on Hover or Focus — Content that appears on hover (tooltips, dropdown menus, contextual information) must be dismissible, hoverable without disappearing, and persistent.

2.5.3 Label in Name — The accessible name of a button or link must contain its visible label text. A button labeled "Download" with an accessible name of "PDF download function" would fail.

4.1.3 Status Messages — Status messages (form submission confirmations, error alerts, search result counts) must be communicated to assistive technology without requiring the user to move keyboard focus to them.

A government site that achieved 508 conformance under WCAG 2.0 may still fail multiple WCAG 2.1 success criteria in these categories.

The "we pass Section 508" problem

Government agencies that receive federal grants or operate under federal funding agreements often undergo Section 508 assessments as part of their procurement or reporting requirements. Vendors selling software to the federal government provide VPATs — Voluntary Product Accessibility Templates — that document their conformance to 508 standards.

This creates a familiar but misleading frame: "we have a VPAT" or "our vendor is 508 compliant" sounds like an accessibility certification. It isn't. A VPAT documents a vendor's assertion of conformance against Section 508 standards (WCAG 2.0 AA), not against the DOJ Title II rule (WCAG 2.1 AA). A 508-compliant product can still have WCAG 2.1 failures.

More importantly, your agency's website is not the same thing as the software products you procure. The content your team authors, the custom templates your CMS produces, and the integrations you've built on top of off-the-shelf platforms all affect WCAG conformance in ways that vendor VPATs don't cover.

What counts for Title II documentation

Under the DOJ Title II rule, agencies need to demonstrate that their web content meets WCAG 2.1 Level AA — not that their vendors are 508 compliant. The documentation that matters for Title II purposes is:

1. A professional WCAG 2.1 audit that assesses your site's actual content against WCAG 2.1 success criteria. 2. An accessibility statement that accurately reflects your conformance status, describes known limitations, and provides contact information for reporting barriers. 3. A remediation plan for any known failures, with timelines.

A vendor VPAT does not substitute for any of these. A Section 508 assessment of your agency's systems is useful but does not close the gap on WCAG 2.1 requirements.

Where to start

For Florida government agencies, the first step is a realistic assessment of where your site stands against WCAG 2.1 — not WCAG 2.0, not Section 508, and not your CMS vendor's conformance documentation. The quick self-assessment guide covers the free tools and 10-item checklist to get a baseline before engaging a professional auditor.

For a complete picture — including the WCAG 2.1 success criteria that automated tools cannot evaluate — the Parallax WCAG Audit provides a full professional assessment of your site. The deliverable includes a findings report structured by WCAG 2.1 criterion, a remediation roadmap, and a completed WCAG 2.1 accessibility statement that names the auditor. For agencies with existing 508 documentation, the audit also notes where your current 508 conformance addresses 2.1 requirements and where new gaps exist.

The WCAG Pre-Audit Readiness Kit ($149) is a practical starting point if you want to understand your 2.1 exposure before commissioning a full audit. The kit includes a 49-criterion testing checklist, a WCAG 2.1 remediation tracker, an accessibility statement template, a VPAT worksheet, and a procurement guide for Florida agencies evaluating audit vendors.

---

*Morton Technology Consulting LLC, Tallahassee, FL. Questions about Section 508, WCAG 2.1, or DOJ Title II compliance: [email protected].*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →