Washington DC Contractor WCAG Checklist

Technology and Data District of Columbia 3 Minutes Read ยท published February 07, 2026 Flag of District of Columbia

Washington, District of Columbia contractors who build or maintain websites, web apps, or digital services for the city must follow accessible design best practices and federal accessibility law. This checklist explains the technical WCAG expectations commonly required in solicitations and contracts, how enforcement works, and practical steps contractors should take before, during, and after delivery. Use this guide to prepare bids, write accessibility clauses, run tests, document compliance, and respond to complaints.

WCAG basics and when they apply

Many District solicitations require conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 AA or an equivalent standard for web and mobile content. Contractors should confirm the solicitation language and the contract accessibility clause before proposing a solution. The U.S. Access Board publishes standards and guidance used by federal and local governments to map technical requirements to WCAG conformance.[1]

  • Specify WCAG level (for example, WCAG 2.1 AA) in proposals and SOWs.
  • Maintain documentation: VPAT or accessibility conformance report, test results, and remediation logs.
  • Include automated and manual testing: keyboard-only, screen reader, color contrast, and cognitive checks.
  • Provide procurement-ready remediation plans and timelines for defects discovered in acceptance testing.
  • Define acceptance criteria and deadlines for accessibility fixes in contract milestones.
Run accessibility tests early and document results to avoid costly late fixes.

Penalties & Enforcement

Enforcement of digital accessibility obligations involving public services is primarily handled under federal law (Title II of the Americans with Disabilities Act) and by federal agencies; local complaint routes may also exist for District services. Specific monetary fines for contractor noncompliance with WCAG in District contracts are not specified on the cited pages; contractors should rely on contract remedies and federal enforcement mechanisms for obligations and sanctions.[2]

  • Fines and monetary penalties: not specified on the cited page; contractual remedies vary by solicitation.
  • Escalation: first notice, cure period, then potential termination or equitable remedies as set by the contract (not specified on the cited page).
  • Non-monetary sanctions: injunctive relief, corrective action plans, system remediation orders, and court enforcement under ADA Title II or federal law.
  • Enforcers and complaint filing: federal Department of Justice handles Title II accessibility complaints; check the DOJ complaint guidance for filing options and procedures.[2]
  • Inspections and audits: agencies may require documentation, accessibility testing reports, and retesting during acceptance.
If a contract includes an accessibility warranty, follow the contract cure procedures immediately after notification.

Applications & Forms

No single District contractor WCAG compliance form was found on the cited federal guidance pages; contractors typically submit a Voluntary Product Accessibility Template (VPAT) or equivalent conformance report and any agency-specific accessibility attestation required in the solicitation. For federal complaint filing, consult the Department of Justice guidance on filing accessibility complaints.[2]

Checklist for contractor delivery

  • Run automated scans and manual checks against WCAG 2.1 AA success criteria.
  • Fix critical keyboard, focus, and screen-reader failures before client acceptance.
  • Produce a VPAT or accessibility conformance report with evidence and remediation timelines.
  • Include contact for accessibility issues and a process for users to report barriers.
  • Schedule periodic re-tests and include an SLA for accessibility maintenance.
A VPAT documents conformance and is commonly requested by public-sector buyers.

FAQ

Do contractors working for Washington need to meet WCAG?
Often yes: solicitations commonly require conformance to WCAG (typically 2.1 AA) or equivalent; always confirm the solicitation and contract language.
Who enforces accessibility complaints about District digital services?
Federal enforcement under ADA Title II is available through the U.S. Department of Justice; local complaint options through District agencies may also exist.
What documents should I deliver to show compliance?
Provide a VPAT or accessibility conformance report, automated and manual test results, and a remediation log for any outstanding issues.

How-To

  1. Run an initial accessibility audit covering automated scans and manual screen-reader and keyboard tests.
  2. Create a VPAT or conformance report that maps site features to WCAG success criteria.
  3. Prioritize and remediate critical issues, then retest and document fixes.
  4. Include accessibility acceptance criteria and remediation timelines in the contract SOW.
  5. Set up an ongoing monitoring schedule and a clear user feedback channel for accessibility reports.

Key Takeaways

  • Confirm required WCAG level in each solicitation before bidding.
  • Deliver a VPAT and evidence-based test results as part of acceptance.
  • Include remediation SLAs and regular re-testing in maintenance contracts.

Help and Support / Resources

  1. [1] U.S. Access Board - Information and Communication Technology (ICT) Accessibility Standards
  2. [2] U.S. Department of Justice - How to File an ADA Complaint

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data