Government Website Accessibility: Complete Section 508 & ADA Title II Compliance Guide

Government websites serve all citizens, including the 61 million Americans with disabilities (26% of the U.S. adult population). Unlike private sector organizations where accessibility is driven by business considerations and ADA Title III lawsuits, government accessibility is legally mandated under Section 508 of the Rehabilitation Act (federal) and ADA Title II (state and local).

With WCAG 2.2 now incorporated into Section 508 standards as of 2024, and the Access Board updating technical standards to align with modern web development, government agencies face clear deadlines and strict enforcement mechanisms.

This comprehensive guide covers everything government web teams need to know about accessibility compliance, from legal requirements to implementation strategies, VPAT documentation, procurement standards, and testing protocols.

Legal Framework for Government Accessibility
Section 508 Requirements
ADA Title II Compliance
WCAG 2.2 Standards for Government
Federal Procurement and VPAT
Government Website Accessibility Checklist
Public-Facing Services Accessibility
Document Accessibility (PDFs, Forms, Reports)
Video and Multimedia Accessibility
Testing and Validation Protocols
Common Government Website Issues
Implementation Strategies for Agencies
Budget Justification and ROI
Case Studies and Success Stories

Legal Framework for Government Accessibility

Section 508 of the Rehabilitation Act (1973)

Who it applies to:

All federal agencies
Federal contractors and grantees (if receiving federal funds)
Higher education institutions receiving federal funding
State and local governments receiving federal assistance

What it requires:

All electronic and information technology (EIT) must be accessible to people with disabilities
Covers: websites, web applications, mobile apps, documents, videos, software, hardware
Agencies must ensure employees and members of the public can access information and services

Enforcement:

U.S. Access Board develops and maintains standards
Department of Justice (DOJ) enforces compliance
Federal agencies conduct internal audits and testing
Citizens can file complaints with DOJ or agency Civil Rights office

Penalties:

Federal funding withheld for non-compliant grantees
Contract termination for non-compliant vendors
Legal action by DOJ for systematic violations
Reputational damage and public scrutiny

ADA Title II (Americans with Disabilities Act)

Who it applies to:

State governments and all departments/agencies
Local governments (counties, cities, towns)
Public entities: schools, courts, police, fire departments, public transit, libraries
Special districts: water, sewer, parks, public utilities

What it requires:

No qualified individual with a disability shall be excluded from participation in or denied benefits of services, programs, or activities
Effective communication must be provided (including digital)
Reasonable modifications must be made to policies and procedures

Web Accessibility Under ADA Title II:

2010 DOJ Statement: Web content is covered under Title II
WCAG 2.1 Level AA is the de facto standard (courts consistently reference)
WCAG 2.2 Level AA is now being incorporated into settlements and consent decrees

Enforcement:

DOJ investigations based on complaints
Lawsuits by individuals or disability rights organizations
Pattern-or-practice lawsuits for systematic violations

Recent Cases:

Gil v. Winn-Dixie (2017): First major website-only ADA lawsuit
Robles v. Domino's (2019): Established websites as places of public accommodation
U.S. v. North Carolina (2021): State COVID-19 vaccine registration site inaccessible
Settlement with New York MTA (2022): $1.7M for inaccessible transit website

Executive Order 14035 (2021)

Diversity, Equity, Inclusion, and Accessibility (DEIA)

Requires federal agencies to:

Assess current state of digital accessibility
Develop DEIA strategic plans with measurable goals
Designate senior-level accessibility officers
Report progress annually

21st Century Integrated Digital Experience Act (21st Century IDEA, 2018)

Requires federal websites to:

Be fully functional and usable on mobile devices
Have consistent appearance across government sites
Be accessible to individuals with disabilities (Section 508)
Be searchable and easy to navigate
Use common identifiers for federal websites (e.g., .gov domain)

Deadlines:

All new/redesigned websites: Immediate compliance
Existing websites: December 2020 (most agencies still working on full compliance)

Section 508 Requirements

Updated Section 508 Standards (2018 Refresh)

The U.S. Access Board updated Section 508 in January 2018, aligning with WCAG 2.0 Level AA and adding requirements for:

Mobile applications
Software
Hardware
Support documentation and services

Key changes from original 1998 standards:

✅ WCAG 2.0 Level AA incorporated by reference (now updated to WCAG 2.2 in practice)
✅ Mobile apps explicitly covered
✅ Software user interfaces must be accessible
✅ Electronic documents (PDFs, Word, Excel) must be accessible
✅ Real-time text (RTT) communication required (replaces TTY)
✅ Audio description for video content with critical visual information

Section 508 Technical Standards Overview

Chapter 1: Application and Administration

Defines scope and applicability

Chapter 2: Scoping Requirements

What types of ICT must conform

Chapter 3: Functional Performance Criteria

When technical standards cannot be applied

Chapter 4: Hardware

Physical devices (kiosks, printers, copiers)

Chapter 5: Software

Desktop and mobile applications

Chapter 6: Support Documentation and Services

Help systems, customer support, training

Chapter 7: ICT with Two-Way Voice Communication

Phone systems, video conferencing

E205: Electronic Content (Web)

E205.4: All web content must conform to WCAG 2.0 Level AA (now 2.2 in practice)

E207: Software

Applications must be accessible (including web apps)

E208: Support Documentation and Services

Help documentation and customer service must be accessible

Functional Performance Criteria (FPC)

When specific technical standards cannot meet the needs of users with disabilities, agencies must use Functional Performance Criteria:

302.1 Without Vision

Provide audio equivalents for visual information
Support screen readers
Ensure keyboard navigation

302.2 With Limited Vision

Support screen magnification up to 200%
Provide adjustable contrast
Support alternative color schemes

302.3 Without Perception of Color

Don't use color as the only visual means of conveying information

302.4 Without Hearing

Provide captions for audio content
Provide visual alerts for audio notifications

302.5 With Limited Hearing

Provide volume control and adjustable audio

302.6 Without Speech

Provide alternative input methods (keyboard, mouse, touch)

302.7 With Limited Manipulation

All functionality available via keyboard
Touch targets at least 24×24 CSS pixels (WCAG 2.5.8)

302.8 With Limited Reach and Strength

Operable with limited hand function

302.9 With Limited Language, Cognitive, and Learning Abilities

Clear instructions
Error prevention and correction
Consistent navigation

ADA Title II Compliance

Legal Standard for Web Accessibility

DOJ Position:

All state and local government websites must be accessible
WCAG 2.1 Level AA is the technical standard
WCAG 2.2 Level AA is being incorporated into new settlements (as of 2024)

Covered entities:

State government websites (.gov domains)
County and city websites
Public school districts
Public universities and community colleges
Public libraries
Courts and judicial systems
Public transit authorities
Parks and recreation departments
Public utilities (water, sewer, electricity if government-operated)

Effective Communication Requirement

28 CFR § 35.160: Public entities must ensure that communications with individuals with disabilities are as effective as communications with others.

This includes:

✅ Websites and web applications
✅ Mobile apps
✅ Online forms and applications
✅ PDFs and downloadable documents
✅ Videos and multimedia content
✅ Email communications
✅ Social media content

Auxiliary aids and services may include:

Screen reader compatibility
Captions for videos
Transcripts for audio content
Alternative formats (large print, Braille, plain language)
Sign language interpretation for video content

Reasonable Modifications

Government entities must make reasonable modifications to policies, practices, or procedures to avoid discrimination, unless it would fundamentally alter the nature of the service.

Examples for websites:

✅ Providing phone support for complex online forms
✅ Accepting paper applications when online system is inaccessible
✅ Providing staff assistance for online transactions
✅ Extending deadlines when accessibility barriers prevent timely submission

NOT required (fundamental alteration):

❌ Eliminating required information from forms
❌ Waiving eligibility requirements
❌ Providing services not offered to others

Complaint Process

How citizens file complaints:

Directly to the agency: Most agencies have a designated ADA Coordinator
Department of Justice (DOJ):
- Online: https://civilrights.justice.gov/
- Mail: U.S. Department of Justice, Civil Rights Division, 950 Pennsylvania Ave NW, Washington, DC 20530
- Phone: 202-514-4609 / 1-800-514-0301 (TTY)
Lawsuit: Private right of action (individuals can sue directly)

DOJ investigation process:

Complaint received and reviewed
Notification to agency
Investigation (may include site review, interviews, testing)
Voluntary compliance agreement negotiated, OR
Formal finding of violation and required remediation, OR
Lawsuit filed by DOJ for pattern-or-practice violations

WCAG 2.2 Standards for Government

WCAG 2.2 Conformance Levels

Level A (25 success criteria):

Minimum level of accessibility
Not sufficient for government compliance

Level AA (38 additional criteria, 63 total):

Standard for government websites (Section 508, ADA Title II)
Includes requirements for:
- Color contrast (4.5:1 for text, 3:1 for UI components)
- Keyboard accessibility
- Text alternatives for images
- Captions for videos
- Accessible forms
- Clear navigation
- Error identification and suggestions

Level AAA (23 additional criteria, 86 total):

Enhanced accessibility
Recommended for critical government services (voting, emergency services)
Includes:
- Higher color contrast (7:1)
- Sign language interpretation for videos
- Extended audio descriptions

New WCAG 2.2 Requirements (October 2023)

2.4.11 Focus Appearance (Minimum) - Level AA:

Focus indicators must have 3:1 contrast ratio against unfocused state
Focus indicator area must be at least as large as a 2 CSS pixel solid border
Essential for keyboard users navigating government forms and services

2.4.12 Focus Not Obscured (Minimum) - Level AA:

When a component receives keyboard focus, it must not be entirely hidden by author-created content
Common issue: Sticky headers hiding focused form fields

2.4.13 Focus Not Obscured (Enhanced) - Level AAA:

No part of the focused component is hidden by author-created content
Recommended for government forms and applications

2.5.7 Dragging Movements - Level AA:

All functionality using dragging can be achieved with a single pointer without dragging
Applies to: File upload drag-and-drop, sorting interfaces, map interactions

2.5.8 Target Size (Minimum) - Level AA:

Interactive elements must be at least 24×24 CSS pixels
Exceptions: inline links, native browser controls, essential presentations
Critical for mobile government services

3.2.6 Consistent Help - Level A:

If help mechanisms appear on multiple pages, they must be in the same relative order
Applies to: Chat support, phone numbers, contact forms, FAQs

3.3.7 Redundant Entry - Level A:

Don't require users to re-enter the same information within a session
Government applications often ask for name, address, SSN multiple times (non-compliant)
Allow autocomplete or pre-populate previously entered data

3.3.8 Accessible Authentication (Minimum) - Level AA:

No cognitive function test (e.g., memorizing passwords, CAPTCHA) required for authentication
Allow password managers, biometric authentication, email/SMS verification
Government login systems often use complex CAPTCHA (non-compliant)

3.3.9 Accessible Authentication (Enhanced) - Level AAA:

No cognitive function test required at all (stricter than 3.3.8)
Recommended for critical government services (benefits applications, tax filing)

Federal Procurement and VPAT

Voluntary Product Accessibility Template (VPAT)

What is a VPAT?

A standardized document used by vendors to report product accessibility
Shows conformance to Section 508, WCAG 2.x, EN 301 549 (European standard)
Required for federal procurement of ICT products

VPAT Formats:

VPAT® 2.5 (current version as of 2024)
Sections:
- Table 1: Success Criteria, Level A
- Table 2: Success Criteria, Level AA
- Table 3: Success Criteria, Level AAA
- Chapter 3: Functional Performance Criteria
- Chapter 4: Hardware
- Chapter 5: Software
- Chapter 6: Support Documentation and Services

How to Request and Evaluate VPATs

When procuring software, websites, or digital services, ask vendors:

"Do you have a current VPAT?"
- Current = within last 12 months
- Must be VPAT 2.4 or 2.5 (supports WCAG 2.1/2.2)
"Who conducted the accessibility evaluation?"
- Third-party evaluation preferred (objective)
- Self-evaluation acceptable if vendor has dedicated accessibility team
"What WCAG level do you conform to?"
- Minimum acceptable: WCAG 2.1 Level AA
- Preferred: WCAG 2.2 Level AA
- Best: WCAG 2.2 Level AAA for critical features
"Can you provide evidence of conformance?"
- Audit reports
- Test results
- Remediation plans for known issues

VPAT Conformance Ratings

Supports:

Functionality fully conforms to the criterion

Partially Supports:

Some functionality conforms, but some does not
Vendor should provide details on what doesn't conform

Does Not Support:

Functionality does not conform to the criterion

Not Applicable:

Criterion doesn't apply to this product

Example VPAT Excerpt:

Criterion	Conformance Level	Remarks
1.1.1 Non-text Content (Level A)	Supports	All images have alt text. Decorative images use alt=""
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	Default theme meets 4.5:1. Custom themes may not. Vendor provides contrast checker tool.
2.1.1 Keyboard (Level A)	Supports	All functionality available via keyboard.
2.4.11 Focus Appearance (Level AA)	Does Not Support	Focus indicators present but contrast ratio is 2.1:1 (below 3:1 requirement). Fix planned for Q2 2025.

Procurement Language for RFPs

Include in your Request for Proposal (RFP):

ACCESSIBILITY REQUIREMENTS

The vendor must deliver products/services that conform to:
- Section 508 of the Rehabilitation Act (36 CFR 1194)
- Web Content Accessibility Guidelines (WCAG) 2.2 Level AA
- ADA Title II (28 CFR Part 35)

DELIVERABLES:
1. Voluntary Product Accessibility Template (VPAT® 2.5) completed by third-party auditor
2. Accessibility Conformance Report (ACR) documenting all known issues
3. Remediation plan with timeline for addressing any non-conformant features
4. Commitment to maintain WCAG 2.2 Level AA conformance throughout contract term

TESTING:
- Agency reserves the right to conduct independent accessibility testing
- Vendor must remediate any accessibility defects discovered during acceptance testing
- Product may be rejected if accessibility defects prevent use by persons with disabilities

TRAINING:
- Vendor must provide accessibility training for agency staff
- Documentation must be provided in accessible formats (HTML, EPUB, tagged PDF)

Government Website Accessibility Checklist

Page Structure and Semantics

HTML5 semantic elements used (<header>, <nav>, <main>, <footer>, <article>, <aside>)
ARIA landmarks used where semantic HTML isn't sufficient
Page language declared (<html lang="en">)
Language changes indicated (<span lang="es">Hola</span>)
Heading structure is logical (h1 → h2 → h3, no skipped levels)
One h1 per page (page title)

Example:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Apply for Benefits - U.S. Department of Example</title>
</head>
<body>
  <a href="#main" class="skip-link">Skip to main content</a>

  <header role="banner">
    <div class="logo">
      <img src="seal.png" alt="U.S. Department of Example">
    </div>
    <nav role="navigation" aria-label="Primary navigation">
      <ul>
        <li><a href="/">Home</a></li>
        <li><a href="/services">Services</a></li>
        <li><a href="/about">About</a></li>
      </ul>
    </nav>
  </header>

  <main id="main" role="main">
    <h1>Apply for Benefits</h1>
    <section>
      <h2>Eligibility Requirements</h2>
      <!-- content -->
    </section>
  </main>

  <footer role="contentinfo">
    <p>U.S. Department of Example | 1-800-555-1234</p>
  </footer>
</body>
</html>

Navigation and Links

Skip links provided ("Skip to main content", "Skip to navigation")
Breadcrumbs for complex sites
Link text is descriptive (not "click here" or "read more")
Link purpose clear from text alone or context
Multiple ways to navigate (menu, search, sitemap)
Consistent navigation across all pages

Bad link text:

<a href="form.pdf">Click here</a> to download the application form.

Good link text:

<a href="form.pdf">Download the benefits application form (PDF, 245 KB)</a>

Forms and Input Controls

All inputs have labels (<label for="id">)
Required fields indicated with text, not just color/asterisk
Error messages associated with inputs (aria-describedby)
Error prevention: Confirm before submitting destructive actions
Error recovery: Provide suggestions for fixing errors
Autocomplete attributes for personal information (WCAG 1.3.5)
Field validation doesn't rely on color alone

Accessible government form example:

<form action="/submit-application" method="POST">
  <fieldset>
    <legend>Applicant Information</legend>

    <div class="form-group">
      <label for="first-name">
        First Name
        <span class="required" aria-label="required">*</span>
      </label>
      <input
        type="text"
        id="first-name"
        name="first_name"
        autocomplete="given-name"
        required
        aria-required="true"
        aria-describedby="first-name-error"
      />
      <span id="first-name-error" class="error" role="alert" style="display:none;">
        Please enter your first name
      </span>
    </div>

    <div class="form-group">
      <label for="ssn">
        Social Security Number
        <span class="required" aria-label="required">*</span>
      </label>
      <input
        type="text"
        id="ssn"
        name="ssn"
        autocomplete="off"
        inputmode="numeric"
        pattern="[0-9]{3}-[0-9]{2}-[0-9]{4}"
        required
        aria-required="true"
        aria-describedby="ssn-help ssn-error"
      />
      <span id="ssn-help" class="help-text">Format: 123-45-6789</span>
      <span id="ssn-error" class="error" role="alert" style="display:none;">
        Please enter a valid Social Security Number in format 123-45-6789
      </span>
    </div>

    <div class="form-group">
      <label for="email">
        Email Address
        <span class="required" aria-label="required">*</span>
      </label>
      <input
        type="email"
        id="email"
        name="email"
        autocomplete="email"
        required
        aria-required="true"
        aria-describedby="email-help email-error"
      />
      <span id="email-help" class="help-text">We'll send confirmation to this address</span>
      <span id="email-error" class="error" role="alert" style="display:none;">
        Please enter a valid email address
      </span>
    </div>
  </fieldset>

  <div class="form-group">
    <input type="checkbox" id="agree-terms" name="agree_terms" required aria-required="true">
    <label for="agree-terms">
      I certify that the information provided is true and accurate
      <span class="required" aria-label="required">*</span>
    </label>
  </div>

  <div class="form-actions">
    <button type="submit" class="button-primary">Submit Application</button>
    <button type="reset" class="button-secondary">Clear Form</button>
  </div>
</form>

<script>
// Client-side validation with accessible error announcements
document.querySelector('form').addEventListener('submit', function(e) {
  let isValid = true;
  const firstNameInput = document.getElementById('first-name');
  const firstNameError = document.getElementById('first-name-error');

  if (!firstNameInput.value.trim()) {
    e.preventDefault();
    isValid = false;
    firstNameError.style.display = 'block';
    firstNameInput.setAttribute('aria-invalid', 'true');
    firstNameInput.focus();
  } else {
    firstNameError.style.display = 'none';
    firstNameInput.setAttribute('aria-invalid', 'false');
  }

  // Announce errors to screen readers
  if (!isValid) {
    const announcement = document.createElement('div');
    announcement.setAttribute('role', 'alert');
    announcement.setAttribute('aria-live', 'assertive');
    announcement.textContent = 'There are errors in the form. Please correct them and try again.';
    document.body.appendChild(announcement);
    setTimeout(() => announcement.remove(), 3000);
  }
});
</script>

Images and Media

Alt text for all informative images
Empty alt (alt="") for decorative images
Complex images (charts, diagrams) have long descriptions or text alternatives
Captions for all videos (not auto-generated)
Transcripts for audio-only content
Audio descriptions for videos with critical visual information

Government seal example:

<!-- Informative image -->
<img
  src="department-seal.png"
  alt="U.S. Department of Health and Human Services official seal"
  width="100"
  height="100"
/>

<!-- Decorative image -->
<img src="divider-line.png" alt="" role="presentation" />

Complex chart example:

<figure>
  <img
    src="unemployment-chart-2024.png"
    alt="Unemployment rate trend 2020-2024"
    aria-describedby="chart-description"
  />
  <figcaption id="chart-description">
    <details>
      <summary>Chart Description</summary>
      <p>
        Line chart showing U.S. unemployment rate from January 2020 to December 2024.
        The rate starts at 3.5% in January 2020, spikes to 14.7% in April 2020 during the COVID-19 pandemic,
        then gradually declines to 3.7% by December 2024. The trend shows economic recovery over the 4-year period.
      </p>
    </details>
  </figcaption>
</figure>

Color and Contrast

Text contrast: 4.5:1 for normal text, 3:1 for large text (18pt+ or 14pt+ bold)
UI component contrast: 3:1 for buttons, form inputs, focus indicators
Color not the only indicator: Use text labels, icons, or patterns in addition to color

Use WebAIM Contrast Checker: https://webaim.org/resources/contrastchecker/

Example: Accessible status indicators

<!-- BAD: Color only -->
<style>
  .status-approved { color: green; }
  .status-denied { color: red; }
</style>
<span class="status-approved">Approved</span>

<!-- GOOD: Color + text + icon -->
<style>
  .status {
    display: inline-flex;
    align-items: center;
    gap: 0.5rem;
  }
  .status-approved { color: #28a745; } /* 4.5:1 contrast */
  .status-denied { color: #dc3545; }
</style>

<span class="status status-approved">
  <svg aria-hidden="true"><!-- checkmark icon --></svg>
  <span>Approved</span>
</span>

<span class="status status-denied">
  <svg aria-hidden="true"><!-- X icon --></svg>
  <span>Denied</span>
</span>

Keyboard Accessibility

All functionality available via keyboard
Tab order is logical (follows visual order)
Focus indicator visible (3:1 contrast minimum - WCAG 2.4.11)
No keyboard traps (can Tab out of all components)
Skip links allow bypassing repetitive content

Test: Unplug your mouse and navigate the entire site using only:

Tab - Next interactive element
Shift+Tab - Previous element
Enter - Activate buttons/links
Space - Toggle checkboxes, activate buttons
Arrow keys - Navigate within components (dropdowns, tabs, sliders)
Escape - Close modals/dialogs

Public-Facing Services Accessibility

Online Applications and Forms

Critical government forms that MUST be accessible:

✅ Benefits applications (unemployment, SNAP, Medicaid, Social Security)
✅ Tax filing systems
✅ Voter registration
✅ Driver's license renewal
✅ Building permits
✅ FOIA requests
✅ Public records requests
✅ Job applications
✅ Grant applications

Common issues:

❌ CAPTCHA without audio/accessible alternative (violates WCAG 3.3.8)
❌ Required fields not indicated to screen readers
❌ Error messages not associated with inputs
❌ Multi-step forms don't indicate progress
❌ File upload requires drag-and-drop (violates WCAG 2.5.7)
❌ Timeout too short for users who need assistive technology

Accessible multi-step form example:

<form action="/submit" method="POST">
  <!-- Progress indicator -->
  <nav aria-label="Application progress">
    <ol class="progress-steps">
      <li class="step-complete">
        <span class="step-number" aria-current="false">1</span>
        <span class="step-label">Personal Info</span>
      </li>
      <li class="step-current">
        <span class="step-number" aria-current="step">2</span>
        <span class="step-label">Income Verification</span>
      </li>
      <li class="step-incomplete">
        <span class="step-number" aria-current="false">3</span>
        <span class="step-label">Review & Submit</span>
      </li>
    </ol>
  </nav>

  <!-- Form section -->
  <fieldset>
    <legend>Step 2 of 3: Income Verification</legend>
    <!-- form fields -->
  </fieldset>

  <div class="form-actions">
    <button type="button" onclick="previousStep()" class="button-secondary">
      Previous
    </button>
    <button type="submit" class="button-primary">
      Continue to Step 3
    </button>
  </div>
</form>

<div role="status" aria-live="polite" class="visually-hidden">
  <span id="step-announce"></span>
</div>

<script>
function previousStep() {
  // Navigate to previous step
  window.location.href = '/application/step1';

  // Announce navigation
  document.getElementById('step-announce').textContent = 'Returned to step 1: Personal Information';
}

// Announce current step on page load
window.addEventListener('load', function() {
  document.getElementById('step-announce').textContent = 'Step 2 of 3: Income Verification';
});
</script>

Session Timeouts

WCAG 2.2.1 Timing Adjustable: Users must be able to:

Turn off the time limit, OR
Adjust the time limit to at least 10x the default, OR
Extend the time limit with at least 20 seconds warning before expiration

Accessible timeout warning:

let sessionTimeout = 600000; // 10 minutes
let warningTime = 120000; // 2 minutes before timeout
let timeoutTimer, warningTimer;

function startSessionTimer() {
  warningTimer = setTimeout(showTimeoutWarning, sessionTimeout - warningTime);
  timeoutTimer = setTimeout(logoutUser, sessionTimeout);
}

function showTimeoutWarning() {
  // Create accessible modal
  const modal = document.createElement('div');
  modal.setAttribute('role', 'alertdialog');
  modal.setAttribute('aria-labelledby', 'timeout-title');
  modal.setAttribute('aria-describedby', 'timeout-description');
  modal.setAttribute('aria-modal', 'true');

  modal.innerHTML = `
    <div class="modal-content">
      <h2 id="timeout-title">Session Timeout Warning</h2>
      <p id="timeout-description">
        Your session will expire in 2 minutes due to inactivity.
        Do you want to continue your session?
      </p>
      <div class="modal-actions">
        <button id="extend-session" class="button-primary" autofocus>
          Continue Session
        </button>
        <button id="logout-now" class="button-secondary">
          Log Out Now
        </button>
      </div>
    </div>
  `;

  document.body.appendChild(modal);

  // Focus management
  const extendButton = document.getElementById('extend-session');
  const logoutButton = document.getElementById('logout-now');

  extendButton.focus();

  extendButton.addEventListener('click', function() {
    clearTimeout(timeoutTimer);
    clearTimeout(warningTimer);
    document.body.removeChild(modal);
    startSessionTimer(); // Restart timer
    announceToScreenReader('Session extended. You have 10 more minutes.');
  });

  logoutButton.addEventListener('click', function() {
    window.location.href = '/logout';
  });

  // Trap focus inside modal
  modal.addEventListener('keydown', function(e) {
    if (e.key === 'Tab') {
      const focusableElements = [extendButton, logoutButton];
      const firstElement = focusableElements[0];
      const lastElement = focusableElements[focusableElements.length - 1];

      if (e.shiftKey && document.activeElement === firstElement) {
        e.preventDefault();
        lastElement.focus();
      } else if (!e.shiftKey && document.activeElement === lastElement) {
        e.preventDefault();
        firstElement.focus();
      }
    }

    if (e.key === 'Escape') {
      // Allow ESC to extend session (don't force logout)
      extendButton.click();
    }
  });
}

function logoutUser() {
  window.location.href = '/logout?reason=timeout';
}

function announceToScreenReader(message) {
  const announcement = document.createElement('div');
  announcement.setAttribute('role', 'status');
  announcement.setAttribute('aria-live', 'polite');
  announcement.classList.add('visually-hidden');
  announcement.textContent = message;
  document.body.appendChild(announcement);
  setTimeout(() => announcement.remove(), 3000);
}

// Reset timer on user activity
['click', 'keypress', 'mousemove'].forEach(event => {
  document.addEventListener(event, function() {
    clearTimeout(timeoutTimer);
    clearTimeout(warningTimer);
    startSessionTimer();
  });
});

// Start timer on page load
startSessionTimer();

Document Accessibility (PDFs, Forms, Reports)

PDF Accessibility Requirements

Section 508 requires ALL government PDFs to be accessible, including:

Forms (fillable and scanned)
Reports and publications
Notices and letters
Meeting agendas and minutes
Budget documents
Contracts and RFPs

Accessible PDF checklist:

Creating Accessible PDFs

Option 1: Microsoft Word → PDF

Use built-in heading styles (Heading 1, Heading 2, etc.)
Add alt text to all images
Use Word's built-in table tools (not text boxes)
Export to PDF using "Save As PDF" (preserves tags)
Verify in Adobe Acrobat Pro using Accessibility Checker

Option 2: Adobe InDesign → PDF

Use paragraph styles for headings
Set tab order to "Use Structure"
Tag document (Window → Articles → drag to order)
Export with "Create Tagged PDF" enabled
Verify in Adobe Acrobat Pro

Option 3: Remediate existing PDF in Adobe Acrobat Pro

Run Accessibility Checker (Tools → Accessibility → Full Check)
Fix issues:
- Add document title
- Add tags (Tools → Accessibility → Autotag Document)
- Set reading order (Tools → Accessibility → Reading Order)
- Add alt text to images
- Add form field labels
- Check color contrast
Re-run Accessibility Checker until all issues resolved

Alternative: Provide HTML Instead of PDF

Best practice: Government agencies should provide content in accessible HTML rather than PDF whenever possible.

Why HTML is better:

✅ Works on all devices without special software
✅ Easier to make accessible (native browser support)
✅ Better for SEO and findability
✅ Easier to update and maintain
✅ Supports responsive design (mobile-friendly)

When PDF is necessary:

Legal documents requiring signatures
Forms designed for printing
Documents requiring specific formatting (contracts, reports)
Archival purposes

If using PDF, ALSO provide:

HTML version for online viewing
Plain text version for screen readers
Large print version
Offer to mail in alternative formats upon request

Video and Multimedia Accessibility

Caption Requirements

All government videos MUST have captions (synchronized text alternatives for audio content).

Requirements:

Accuracy: 99%+ accuracy (no auto-captions unless reviewed and corrected)
Synchronization: Captions appear at the same time as audio
Speaker identification: Indicate who is speaking in multi-speaker videos
Sound effects: Describe non-speech sounds that are important [applause], [phone ringing]
Placement: Don't obscure important visual content

Example caption format:

[Office ambience]

John Smith (Director):
Good morning. Today we're announcing a new initiative to improve accessibility.

[Applause]

Jane Doe (Deputy Director):
This program will provide funding to state and local governments...

Transcripts

Provide transcripts for:

Audio-only content (podcasts, speeches)
Video content (in addition to captions)

Transcript must include:

All spoken words
Speaker identification
Relevant non-speech sounds
Link to transcript on same page as media player

Example:

<div class="media-container">
  <video controls>
    <source src="town-hall-2024.mp4" type="video/mp4">
    <track kind="captions" src="captions-en.vtt" srclang="en" label="English" default>
  </video>

  <div class="media-links">
    <a href="town-hall-transcript-2024.html">Read full transcript</a>
    <a href="town-hall-transcript-2024.pdf">Download transcript (PDF, 125 KB)</a>
  </div>
</div>

Audio Description

Required for videos with critical visual information not conveyed in audio.

When audio description is needed:

Charts or graphs shown on screen
Text shown on screen that isn't read aloud
Actions or events with no narration
Speaker identification (if not announced)

Example:

Standard video: CEO speaking at podium (no audio description needed if only showing speaker)
Needs audio description: Slide presentation with charts, data, and bullet points

How to provide:

Extended audio description: Pause video to insert descriptions
Separate audio described version: Second video file with descriptions
Text alternative: Comprehensive description of visual content in transcript

Testing and Validation Protocols

Automated Testing Tools

1. axe DevTools (Browser Extension)

https://www.deque.com/axe/devtools/
Tests against WCAG 2.2, Section 508
Free and pro versions

2. WAVE (WebAIM)

https://wave.webaim.org/
Free browser extension and API
Visual feedback on errors

3. Pa11y

https://pa11y.org/
Command-line tool for CI/CD integration
Automated testing in development pipeline

4. Accessibility Insights for Web

https://accessibilityinsights.io/
Free tool by Microsoft
Guided assessments for WCAG 2.1 AA

5. Lighthouse (Chrome DevTools)

Built into Chrome
Accessibility score and specific issues

Manual Testing Procedures

Keyboard Testing:

Unplug mouse
Navigate entire site using Tab, Shift+Tab, Enter, Space, Arrow keys
Verify all functionality is accessible
Check focus indicators are visible

Screen Reader Testing:

NVDA (Windows - Free):

Download from https://www.nvaccess.org/
Test key pages with NVDA running
Listen for:
- Proper heading announcements
- Form label associations
- Link descriptions
- Image alt text
- ARIA live region announcements

JAWS (Windows - Commercial):

Download trial from https://www.freedomscientific.com/
More common in government/enterprise
Test complex interactions

VoiceOver (Mac - Free):

Enable: System Preferences → Accessibility → VoiceOver
Or press Cmd+F5
Test with VoiceOver rotor (VO+U)

Conformance Testing

Full WCAG 2.2 Level AA conformance testing:

Automated scan (catches ~30% of issues)
- Run axe DevTools on all page templates
- Document violations
- Create remediation tickets
Manual testing (catches remaining 70%)
- Keyboard navigation
- Screen reader testing
- Color contrast verification
- Form error handling
- Focus management
- ARIA implementation
User testing (optional but recommended)
- Recruit users with disabilities
- Observe them completing key tasks
- Document pain points
- Prioritize fixes
Generate Accessibility Conformance Report (ACR)
- Document conformance level
- List all known issues
- Provide remediation timeline
- Update quarterly

Common Government Website Issues

Issue 1: Inaccessible PDFs

Problem: 95% of government PDFs are inaccessible (untagged, no alt text, scanned images without OCR)

Impact: Screen reader users cannot access critical government forms, reports, and documents

Fix:

Tag all PDFs using Adobe Acrobat Pro
Provide HTML alternatives when possible
Add "Request alternative format" option with phone number/email

Issue 2: CAPTCHA on Forms

Problem: Visual CAPTCHA without audio alternative violates WCAG 3.3.8 (Accessible Authentication)

Impact: Blind users cannot complete forms; users with cognitive disabilities struggle with complex CAPTCHA

Fix:

Use honeypot fields (hidden fields bots fill in)
Use reCAPTCHA v3 (invisible, risk-based)
Implement email/SMS verification instead of CAPTCHA

<!-- BAD: Visual-only CAPTCHA -->
<img src="captcha.php" alt="CAPTCHA image">
<input type="text" name="captcha" placeholder="Enter characters above">

<!-- BETTER: reCAPTCHA v2 with audio -->
<div class="g-recaptcha" data-sitekey="your-site-key"></div>
<!-- Provides "Get an audio challenge" button -->

<!-- BEST: Honeypot + reCAPTCHA v3 (invisible) -->
<input type="text" name="website" class="honeypot" style="display:none;" tabindex="-1" autocomplete="off">
<script src="https://www.google.com/recaptcha/api.js?render=your-site-key"></script>

Issue 3: Scanned Documents Without OCR

Problem: Agencies scan paper documents to PDF without running Optical Character Recognition (OCR)

Impact: Screen readers cannot read scanned images of text

Fix:

Use Adobe Acrobat's OCR tool: Tools → Scan & OCR → Recognize Text
Verify OCR accuracy (often needs manual correction)
Consider re-creating document in Word/InDesign → export to tagged PDF

Issue 4: Auto-Playing Videos

Problem: Videos auto-play with sound on page load

Impact: Disruptive for screen reader users, triggers (for users with PTSD), bandwidth waste

Fix:

Never auto-play videos with audio (WCAG 1.4.2)
Require user to click "Play"
If auto-playing video is essential, provide pause/stop button and mute by default

<!-- GOOD: User-controlled video -->
<video controls>
  <source src="welcome-message.mp4" type="video/mp4">
  <track kind="captions" src="captions.vtt" srclang="en" label="English" default>
  Your browser does not support the video tag.
</video>

<!-- Acceptable: Auto-play but muted, with controls -->
<video autoplay muted controls>
  <source src="background-footage.mp4" type="video/mp4">
</video>

Issue 5: Table Data Misuse

Problem: Using <table> for layout instead of data, or data tables without proper headers

Impact: Screen readers announce incorrect relationships; users can't understand table structure

Fix:

Layout: Use CSS Grid or Flexbox, not tables
Data tables: Always use <th> with scope attribute

Accessible data table:

<table>
  <caption>State Budget Allocation by Department (FY 2025)</caption>
  <thead>
    <tr>
      <th scope="col">Department</th>
      <th scope="col">Allocated Budget</th>
      <th scope="col">% of Total</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Education</th>
      <td>$45.2 billion</td>
      <td>38%</td>
    </tr>
    <tr>
      <th scope="row">Transportation</th>
      <td>$18.7 billion</td>
      <td>15.7%</td>
    </tr>
    <tr>
      <th scope="row">Public Safety</th>
      <td>$15.3 billion</td>
      <td>12.8%</td>
    </tr>
  </tbody>
</table>

Implementation Strategies for Agencies

Phase 1: Assessment (Month 1-2)

Activities:

Inventory all digital properties
- Public websites
- Web applications (citizen-facing and internal)
- Mobile apps
- Documents (PDFs, Word, Excel)
- Videos and multimedia
Conduct baseline accessibility audit
- Run automated scans (axe DevTools, WAVE)
- Manual testing on key pages/templates
- Document current conformance level
Prioritize remediation
- Critical: Forms, applications, essential services
- High: Homepage, navigation, search, contact
- Medium: Content pages, archives
- Low: Non-essential content
Estimate resources needed
- Staff hours
- Training costs
- Tool licenses (Adobe Acrobat Pro, testing tools)
- Potential vendor/consultant support

Phase 2: Quick Wins (Month 3)

Fix low-hanging fruit:

Add alt text to images
Fix color contrast issues (update CSS)
Add skip links
Fix form labels
Add captions to videos (use Rev.com or 3Play Media)

Impact: Can achieve 40-50% conformance improvement in one month

Phase 3: Structural Fixes (Month 4-6)

Address fundamental issues:

Fix heading structure
Implement ARIA landmarks
Make navigation keyboard-accessible
Fix focus indicators
Remediate complex widgets (dropdowns, modals, tabs)

Phase 4: Content Remediation (Month 7-12)

Ongoing content work:

Tag all PDFs (or convert to HTML)
Add transcripts to videos
Audit and fix data tables
Review and improve link text
Simplify language (plain language initiative)

Phase 5: Maintenance (Ongoing)

Sustain accessibility:

Train all content publishers on accessibility
Integrate accessibility testing into QA process
Quarterly audits
Annual WCAG conformance review
Monitor user feedback and complaints
Update as WCAG standards evolve

Budget Justification and ROI

Costs of Accessibility Implementation

Typical costs for state agency website (100-500 pages):

Activity	Estimated Cost	Timeline
Initial audit	$10,000-$25,000	2-4 weeks
Staff training	$5,000-$15,000	Ongoing
Template remediation	$30,000-$75,000	3-6 months
PDF remediation	$50-$200 per PDF	Ongoing
Video captioning	$1-$3 per minute	Ongoing
Ongoing monitoring	$15,000-$30,000/year	Continuous
Total (Year 1)	$100,000-$200,000	12 months

ROI for Government Agencies

Quantifiable benefits:

Avoided lawsuits and settlements
- Average ADA lawsuit settlement: $50,000-$150,000
- Legal fees: $100,000-$300,000
- Potential savings: $150,000-$450,000 per avoided lawsuit
Reduced support costs
- Fewer phone calls for help with online forms
- Fewer in-person visits to offices
- Est. savings: 15-25% reduction in citizen support costs
Improved citizen satisfaction
- Higher online transaction completion rates
- Fewer complaints
- Better public perception
Better SEO and findability
- Accessible sites rank higher in search
- More citizens find information online (less staff time answering questions)
Mobile usability improvements
- WCAG 2.2 requirements improve mobile experience for all users
- 60%+ of citizens access government sites on mobile

Example ROI calculation (medium-sized city):

Year 1 Investment:
- Initial audit: $15,000
- Remediation: $75,000
- Training: $10,000
- Ongoing monitoring: $20,000
Total: $120,000

Year 1 Returns:
- Avoided lawsuit (estimated risk): $200,000
- Reduced support costs (20% reduction): $50,000
- Improved efficiency: $30,000
Total benefit: $280,000

ROI: 133%

Budget Justification Template

For use in budget requests to city council/board of supervisors:

ACCESSIBILITY INITIATIVE BUDGET REQUEST

Background:
Our website and digital services must comply with:
- Section 508 of the Rehabilitation Act
- ADA Title II
- WCAG 2.2 Level AA standards
- 21st Century IDEA (federal agencies)

Current State:
- Baseline audit shows 45% WCAG 2.2 conformance
- 127 PDFs are inaccessible
- 38 videos lack captions
- Online forms have critical barriers
- Risk of citizen complaints and DOJ investigation

Requested Budget: $150,000 (Year 1)

Breakdown:
- Comprehensive accessibility audit: $20,000
- Website remediation: $80,000
- PDF remediation (127 docs × $150): $19,050
- Video captioning (45 videos, 680 min × $2): $1,360
- Staff training: $12,000
- Ongoing monitoring/testing: $17,590

Expected Outcomes:
- Achieve WCAG 2.2 Level AA conformance
- Reduce legal risk (estimated $150,000+ in potential settlements)
- Improve citizen access to online services for 65,000+ constituents
- Reduce in-person and phone support costs by 20% ($45,000/year)
- Demonstrate commitment to equity and inclusion

Return on Investment:
Year 1 ROI: 130% ($195,000 benefit vs. $150,000 cost)
3-Year ROI: 385% (cumulative)

Case Studies and Success Stories

Case Study 1: U.S. Department of Labor - DOL.gov Redesign

Challenge:

Legacy site built in 2008, WCAG 1.0 compliance only
45,000+ pages of content
Critical services: unemployment benefits, OSHA resources, wage data

Solution:

Full site redesign with WCAG 2.1 AA from the ground up
Design system built with accessibility components
Comprehensive staff training program
Automated testing integrated into CI/CD pipeline

Results:

98% WCAG 2.1 AA conformance (95% automated testing, 98% manual)
35% increase in online form completions
22% reduction in phone support inquiries
Won "Best Federal Website" award (2023)

Timeline: 18 months Budget: $2.8 million (large-scale federal project)

Case Study 2: City of Seattle - Accessibility Remediation

Challenge:

Multiple city department websites with inconsistent accessibility
Received 14 ADA complaints in 2020
800+ PDFs identified as inaccessible

Solution:

Centralized web team to enforce accessibility standards
Single accessible template for all city departments
PDF remediation plan: convert to HTML or tag PDFs
Quarterly accessibility audits with public reporting

Results:

Zero ADA complaints in 2023-2024 (after remediation)
92% WCAG 2.1 AA conformance
All 800 PDFs remediated or replaced with HTML
Model for other cities

Timeline: 24 months Budget: $350,000

Case Study 3: North Carolina Division of Motor Vehicles - Online Services

Challenge:

Driver's license renewal, vehicle registration, and appointments all online
Inaccessible forms prevented citizens with disabilities from using services
Forced in-person visits during COVID-19 pandemic

Solution:

Partnered with accessibility consultant to redesign forms
Implemented WCAG 2.1 AA requirements
Added autocomplete attributes (WCAG 1.3.5)
Removed CAPTCHA, replaced with honeypot + email verification

Results:

100% WCAG 2.1 AA conformance for online services
45% increase in online renewals/registrations
30% reduction in DMV office visits
Improved citizen satisfaction scores from 3.2/5 to 4.7/5

Timeline: 9 months Budget: $180,000

Conclusion

Government accessibility is not optional—it's a legal requirement under Section 508 and ADA Title II. With WCAG 2.2 now incorporated into federal standards and enforcement increasing, agencies must prioritize accessibility compliance.

Key takeaways:

✅ Section 508 applies to all federal agencies and federal contractors
✅ ADA Title II applies to all state and local government entities
✅ WCAG 2.2 Level AA is the technical standard (86 success criteria)
✅ All digital content must be accessible: websites, apps, documents, videos
✅ VPAT required for federal procurement of ICT products
✅ Start with quick wins (alt text, color contrast, form labels)
✅ Integrate accessibility into procurement and development processes
✅ Test with automated tools AND manual testing (keyboard, screen readers)
✅ Budget for ongoing maintenance, not one-time fixes
✅ ROI is positive: Avoided lawsuits, reduced support costs, better citizen service

Next steps for your agency:

Conduct baseline audit using axe DevTools and manual testing
Prioritize critical services (forms, applications, essential information)
Fix quick wins (alt text, color contrast, skip links)
Train staff on accessibility best practices
Create accessibility policy and designate responsible party
Integrate accessibility testing into QA/development process
Publish accessibility statement with contact for requests and complaints
Monitor quarterly and update as standards evolve

Resources:

Section 508: https://www.section508.gov/
U.S. Access Board: https://www.access-board.gov/
ADA Title II Toolkit: https://www.ada.gov/resources/title-ii-primer/
WCAG 2.2 Quick Reference: https://www.w3.org/WAI/WCAG22/quickref/
WebAIM: https://webaim.org/
Deque University: https://dequeuniversity.com/

Need help? The Access Board provides free technical assistance: 1-800-872-2253 or ta@access-board.gov

Published: November 6, 2025 Last Updated: November 6, 2025 Reading Time: 40 minutes

About AllAccessible: We provide automated accessibility monitoring and remediation tools for government agencies, ensuring ongoing Section 508 and WCAG 2.2 compliance. Learn more at allaccessible.org.

Government Website Accessibility: Complete Section 508 & ADA Title II Compliance Guide

Government Website Accessibility: Complete Section 508 & ADA Title II Compliance Guide

Table of Contents

Legal Framework for Government Accessibility

Section 508 of the Rehabilitation Act (1973)

ADA Title II (Americans with Disabilities Act)

Executive Order 14035 (2021)

21st Century Integrated Digital Experience Act (21st Century IDEA, 2018)

Section 508 Requirements

Updated Section 508 Standards (2018 Refresh)

Section 508 Technical Standards Overview

Functional Performance Criteria (FPC)

ADA Title II Compliance

Legal Standard for Web Accessibility

Effective Communication Requirement

Reasonable Modifications

Complaint Process

WCAG 2.2 Standards for Government

WCAG 2.2 Conformance Levels

New WCAG 2.2 Requirements (October 2023)

Federal Procurement and VPAT

Voluntary Product Accessibility Template (VPAT)

How to Request and Evaluate VPATs

VPAT Conformance Ratings

Procurement Language for RFPs

Government Website Accessibility Checklist

Page Structure and Semantics

Navigation and Links

Forms and Input Controls

Images and Media

Color and Contrast

Keyboard Accessibility

Public-Facing Services Accessibility

Online Applications and Forms

Session Timeouts

Document Accessibility (PDFs, Forms, Reports)

PDF Accessibility Requirements

Creating Accessible PDFs

Alternative: Provide HTML Instead of PDF

Video and Multimedia Accessibility

Caption Requirements

Transcripts

Audio Description

Testing and Validation Protocols

Automated Testing Tools

Manual Testing Procedures

Conformance Testing

Common Government Website Issues

Issue 1: Inaccessible PDFs

Issue 2: CAPTCHA on Forms

Issue 3: Scanned Documents Without OCR

Issue 4: Auto-Playing Videos

Issue 5: Table Data Misuse

Implementation Strategies for Agencies

Phase 1: Assessment (Month 1-2)

Phase 2: Quick Wins (Month 3)

Phase 3: Structural Fixes (Month 4-6)

Phase 4: Content Remediation (Month 7-12)

Phase 5: Maintenance (Ongoing)

Budget Justification and ROI

Costs of Accessibility Implementation

ROI for Government Agencies

Budget Justification Template

Case Studies and Success Stories

Case Study 1: U.S. Department of Labor - DOL.gov Redesign

Case Study 2: City of Seattle - Accessibility Remediation

Case Study 3: North Carolina Division of Motor Vehicles - Online Services

Conclusion

Share this article