San Francisco Website WCAG Compliance Checklist

Technology and Data California 3 Minutes Read ยท published February 06, 2026 Flag of California

Introduction

This checklist explains how organizations in San Francisco, California can align public-facing websites and digital services with the Web Content Accessibility Guidelines (WCAG). It summarizes practical steps, common violations, enforcement pathways, and how to document fixes so you can reduce legal and operational risk while improving access for users with disabilities.

WCAG Checklist for San Francisco Organizations

Use the following prioritized items to review pages and web apps. Start with policies, then remediations, then monitoring.

  • Confirm an organizational web accessibility policy and assigned owner for ongoing compliance.
  • Publish an accessibility statement describing standards (WCAG 2.1 AA or later), contact for reports, and remediation timelines.
  • Ensure keyboard-only operation and visible focus on all interactive controls and navigation.
  • Provide text alternatives: alt text for images, transcripts for audio, and captions for video.
  • Test for color contrast, resizable text, and no reliance solely on color for meaning.
  • Update third-party widgets and ensure embedded documents (PDFs) meet accessibility standards.
  • Maintain accessibility testing records, automated scan reports, and manual test notes for major releases.
  • Adopt a remediation schedule that prioritizes high-traffic and critical-user journeys.
  • Provide an accessible feedback and complaint channel with documented response times.
Start with the most-used pages and services, and fix issues iteratively.

Penalties & Enforcement

San Francisco entities should expect that accessibility issues may lead to enforcement actions at municipal, state, or federal levels, or private litigation. Specific civil penalties and administrative fines for website noncompliance are not specified on a single consolidated San Francisco page; enforcement commonly proceeds through corrective orders, administrative complaints, or civil suits rather than a fixed per-day municipal fine.

  • Enforcers: complaints may be handled by the City department responsible for the service, the Mayor's Office on Disability, or through state/federal civil rights agencies.
  • Typical sanctions: corrective compliance orders, required remediation plans, injunctive relief, and potential court-ordered remedies.
  • Monetary penalties: amounts are not specified on the cited municipal guidance pages for web accessibility; courts or agencies may award damages or penalties under state or federal law where applicable.
  • Escalation: initial notice or demand to remediate is common; repeat or continuing noncompliance can lead to litigation or agency enforcement.
  • Appeals and review: appeals typically follow the administrative route of the enforcing body or ordinary court procedures; time limits vary by forum and are not uniformly specified on a single San Francisco page.
  • Defences/discretion: documented good-faith remediation efforts, reasonable accommodation processes, and published remediation timelines (variances or phased fixes) are influential defenses.
If you receive an accessibility complaint, respond promptly and document all remediation steps.

Applications & Forms

There is no single, universally required City form for reporting website accessibility issues; many departments accept complaints via their online contact or ADA request pages, and some accept emailed reports. Specific form names, numbers, fees, or deadlines are not specified on a single consolidated San Francisco page.

Action Steps

  • Publish an accessibility statement and contact email on your site.
  • Run automated WCAG scans and supplement with manual keyboard and screen reader tests.
  • Create a prioritized remediation plan and schedule public updates on progress.
  • Provide a clear reporting channel and respond to complaints within your stated timeframe.
Document test results and remediation steps to show good-faith compliance efforts.

FAQ

Who is required to make websites accessible in San Francisco?
Public agencies and entities delivering services to San Francisco residents, and private organizations offering services to the public, should ensure accessibility; obligations are enforced through civil rights law and administrative remedies.
Which WCAG level should we meet?
WCAG 2.1 AA is the commonly recommended baseline for legal compliance and procurement; agencies may adopt updated standards over time.
How do I report an inaccessible San Francisco city web page?
Report using the department contact, the Mayor's Office on Disability complaint/contact channel, or the site's accessibility feedback link where provided.

How-To

  1. Inventory public webpages and identify high-priority user journeys.
  2. Run automated tests, then perform manual keyboard and screen reader checks on critical pages.
  3. Publish an accessibility statement and a remediation schedule on your site.
  4. Provide a clear contact for accessibility reports and respond within your stated timeline.
  5. Maintain records of tests and fixes and update the public when major items are completed.

Key Takeaways

  • Start remediation on high-traffic and critical-user pages first.
  • Document tests and fixes to demonstrate good-faith efforts.
  • Provide an accessible reporting channel and respond promptly.

Help and Support / Resources

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