Back to reviews and guides

Section 508 Lawsuits: What Organisations Need to Know

This guide explains how Section 508 lawsuits arise, who must comply, and what standards apply. It gives a practical compliance checklist, vendor and procurement advice, and step-by-step workflows for remediation and legal triage.

Section 508 lawsuits: what organisations need to know

Section 508 lawsuits appear when electronic and information technology is not accessible for people with disabilities. Federal agencies, contractors and suppliers face risk if they ignore the Section 508 Standards. This guide explains who is covered, what triggers complaints, practical prevention steps and a response plan if a claim arrives.

Who Section 508 covers

Section 508 is a federal accessibility requirement for electronic and information technology used by federal entities. Organisations that must pay attention include:

  • Federal agencies that develop, procure, maintain or use electronic information technology
  • Companies that supply products or services to federal agencies under contract
  • Subcontractors when the prime contract requires accessible deliverables

What the standards require

The Section 508 Standards reference web accessibility success criteria based on WCAG. For web and software, agencies commonly expect compliance with WCAG Level A and AA success criteria. The standards also cover documents, multimedia, hardware and telephony features. Use of WAI-ARIA is relevant when web components require accessibility roles and states.

How Section 508 lawsuits and complaints typically arise

Complaints and claims often start with an inaccessible website, portal or a vendor product that fails to work with assistive technology. Common triggers are:

  • Procured software whose Vendor Accessibility Documentation or VPAT is inaccurate or missing
  • Public-facing or internal portals that break basic keyboard navigation or lack text alternatives
  • PDFs and documents that are not tagged for screen readers
  • Failure to meet procurement contract terms about accessibility or to provide timely remediation

Enforcement can take several forms. An individual or organisation may file an agency-level complaint where the agency investigates accessibility of its technology. In some cases disputes reach federal court or involve other administrative processes. Separately, many private suits use the ADA rather than Section 508 because the ADA applies to places of public accommodation. Organisations should not rely on one route; addressing accessibility early reduces both administrative complaints and litigation risk.

Common mistakes organisations make

  • Relying only on automated scanning tools and ignoring manual testing with assistive tech
  • Accepting vendor VPATs without validating claims or running independent tests
  • Publishing inaccessible documents and forms without offering accessible alternatives
  • Not including enforceable accessibility requirements in contracts and purchase orders
  • Failing to document remediation efforts and timelines after a complaint

Practical compliance checklist

Use this checklist to reduce the chance of Section 508 lawsuits. Treat it as operational, not legal, guidance.

  1. Adopt a single technical baseline: require WCAG 2.0 Level A and AA as the minimum for web content, and note when higher guidance is expected.
  2. Create or update an accessibility policy and publish an accessibility statement for services and products.
  3. Require a current VPAT from vendors and verify claims with a sampling of independent tests.
  4. Run automated scans followed by manual testing with keyboard navigation and at least one screen reader.
  5. Ensure PDFs and office documents are tagged and tested for reading order and language attributes.
  6. Keep an issues log with priorities, owners, target dates and proof of fixes.
  7. Train procurement, product and legal teams on how accessibility requirements affect contracts and deliverables.

Vendor management and procurement clauses

Good procurement language cuts dispute risk. Require these items in contracts and orders:

  • An explicit accessibility warranty tied to the Section 508 Standards and reference to WCAG success criteria
  • Delivery of a current VPAT and test evidence from the vendor
  • A remediation schedule with liquidated damages or holdbacks for missed delivery if appropriate
  • Obligation to update software to maintain accessibility during the contract term
  • Access to source deliverables or documentation necessary to complete remediation

Testing methods that reduce risk

Combine tools and people. A robust testing approach includes:

  • Automated scanners for broad coverage of common issues
  • Manual verification of flagged items and of areas automated tools miss
  • User testing with people who use screen readers, magnifiers, voice control or switch devices
  • Assistive-technology compatibility checks including keyboard only and ARIA state tests
  • Document and PDF checks with tagging, reading order and language attributes validated

Information gain: step-by-step remediation workflow after a complaint

This workflow is practical for product teams and compliance officers when a complaint arrives.

  1. Record and acknowledge the complaint immediately. Log the date, source and scope.
  2. Freeze public-facing changes to the affected asset while you assess the issue.
  3. Scope the failure. Identify pages, components, documents or files that fail and list the specific WCAG success criteria implicated.
  4. Run a quick proof test with keyboard and a screen reader to confirm the user impact.
  5. Build a short remediation plan with A, B and C fixes. A fixes are quick, high-impact items such as alt text and keyboard traps. B fixes require development time. C fixes are larger refactors.
  6. Provide interim accommodations while you remediate. Examples are an accessible PDF, a plain-text form, or a telephone contact for the task.
  7. Implement fixes, then run regression tests, including user testing where feasible.
  8. Publish a closure note in your issue log and share remediation evidence with the complainant and your agency contact.

If you receive a formal complaint or lawsuit, use this triage framework. It helps you prioritise actions while you involve legal counsel.

  1. Bring together a small response team: legal counsel, accessibility lead, product owner and procurement lead.
  2. Preserve all records related to the matter, including VPATs, test reports, contracts and communications.
  3. Assess immediate operational impact and whether interim fixes can reduce harm to users.
  4. Decide quickly if an early remediation offer is appropriate. Many disputes resolve faster when a credible remediation plan is on the table.
  5. Track timelines closely and communicate status updates internally and to the complainant where allowed by counsel.

Documentation to retain

Maintain these records to show good-faith compliance efforts and to speed response to claims:

  • Accessibility statements and policies
  • VPATs and vendor test reports
  • Automated scan outputs and manual test notes
  • User test consent forms and session notes
  • Issue logs, remediation plans and proof of fixes
  • Procurement documents with accessibility clauses and change orders

Training and governance

Embed accessibility into daily work. Appoint a named accessibility coordinator. Provide role-specific training for designers, developers, procurement and content authors. Review accessibility during release gates and procurement reviews. Governance reduces the chance of Section 508 lawsuits and improves usability for everyone.

When to get external help

Call specialists when you need independent testing, legal interpretation of federal obligations or a remediation partner for code fixes. Independent auditors can validate vendor VPATs and produce user test reports that carry weight in administrative reviews.

Final practical checklist

  • Set WCAG 2.0 A/AA as the baseline and document exceptions
  • Require and verify VPATs from suppliers
  • Run combined automated and manual tests, including assistive technology
  • Keep a remediation log and publish an accessibility statement
  • Include clear accessibility clauses in contracts with remediation timelines
  • Train staff and appoint an accessibility coordinator
  • Have a documented triage and remediation workflow for complaints

If your organisation follows these steps it will reduce the risk of Section 508 lawsuits and make digital services more reliable for all users. For legally binding advice, contact qualified counsel familiar with federal accessibility law.