Washington WCAG Website Accessibility Rules

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

Washington, District of Columbia requires that District government websites follow recognized web accessibility standards and publish a process for reporting and remediation. This guide summarizes the District’s web accessibility policy for municipal sites, identifies the enforcing office, explains enforcement and appeals, and lists practical steps site owners and managers should follow to meet WCAG conformance expectations. It is written for city staff, contractors, nonprofit partners, and members of the public who need clear directions to report problems or to make a site accessible.

If you find inaccessible content on a District site, report it to the specified office for remediation.

Scope and Standards

District guidance for municipal websites references WCAG as the technical standard to guide accessibility of web content and digital services. Implementation expectations, testing approaches, and remediation timelines are managed by the District technology office and relevant program owners.

Primary official technical guidance for District government digital properties is published by the Office of the Chief Technology Officer (OCTO). OCTO Web Accessibility[1]

Penalties & Enforcement

Enforcement for compliance of District government websites is administered through agency oversight and central technology governance. The official OCTO policy page describes obligations and reporting but does not list monetary fines on that page.

  • Enforcer: Office of the Chief Technology Officer (OCTO) and individual agency CIOs for their respective sites.
  • Complaint pathway: report accessibility issues via the OCTO web accessibility contact methods published on the OCTO page.
  • Appeals/review: not specified on the cited page; follow agency review channels or contact OCTO for escalation.
  • Fines and monetary penalties: not specified on the cited page.
  • Escalation for repeat or continuing offences: not specified on the cited page.
  • Non-monetary sanctions: orders to remediate, agency-level corrective plans, and potential administrative or contractual remedies for vendors.
Specific fine amounts and statutory penalty schedules are not published on OCTO’s web accessibility page.

Applications & Forms

No separate public application form to request exemptions or variances from WCAG requirements is published on OCTO’s web accessibility page; agencies typically accept accessibility reports or remediation requests through the contact methods shown on that page.

Common Violations and Typical Outcomes

  • Missing alternative text on images — requires remediation and retest.
  • Poor keyboard navigation — remediation plan and accessibility testing.
  • Insufficient color contrast — fix styling and document changes.
  • Broken skip links or ARIA misuse — code fixes and validation.

Action Steps for Compliance

Practical steps for agencies, contractors, and site managers:

  • Perform an initial audit using automated and manual WCAG testing tools.
  • Create a prioritized remediation plan with deadlines and responsible persons.
  • Budget for ongoing accessibility testing and procurement language requiring WCAG conformance.
  • Establish a public contact point for reporting accessibility problems and respond promptly.

FAQ

Which standard must District government websites meet?
District guidance references the Web Content Accessibility Guidelines (WCAG) as the technical standard for web accessibility; refer to OCTO’s web accessibility page for agency-specific expectations.
How do I report an inaccessible District website?
Report issues following the contact and reporting instructions on the OCTO web accessibility page; OCTO manages central guidance and agency contacts for remediation.
Are there fines for noncompliance?
The OCTO web accessibility page does not list monetary fines or a penalty schedule; see agency procurement or legal guidance for contract remedies.

How-To

  1. Run an automated accessibility scan to identify obvious issues like missing alt text and contrast failures.
  2. Perform manual testing for keyboard navigation and screen-reader compatibility.
  3. Draft a remediation plan that assigns responsibility, sets deadlines, and schedules retesting.
  4. Publish a public accessibility statement on the site and maintain a contact method for reports.
  5. If remediation is not completed, submit a formal complaint using the OCTO contact method on the official page.

Key Takeaways

  • OCTO provides central web accessibility guidance for District government sites.
  • No public fine schedule appears on OCTO’s accessibility page; enforcement focuses on remediation.
  • Establish clear reporting and remediation processes and publish an accessibility statement.

Help and Support / Resources

  1. [1] District of Columbia Office of the Chief Technology Officer - Web Accessibility (current as of February 2026)

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