Website ADA Compliance in San Francisco: Website Requirements Explained

Website ADA compliance in San Francisco — quick overview

Website ADA compliance in San Francisco means making your website usable by people with disabilities and reducing legal risk under federal and state civil-rights laws. The practical target for most organisations is to meet the technical success criteria in WCAG 2.1 AA and to document the work you do. This article explains which laws and standards matter, the common failures I see, and a step-by-step remediation plan you can follow.

Which laws and standards apply

At the federal level, Title III of the Americans with Disabilities Act covers places of public accommodation. Technical success criteria are not set in the ADA text, so courts and settlements commonly use WCAG 2.1 AA as the de facto standard.

California civil-rights statutes such as the Unruh Civil Rights Act and the Disabled Persons Act can also apply to digital access. Public agencies and local government websites in San Francisco have explicit accessibility obligations and published policies to follow.

Who in San Francisco needs to comply

Common groups that must address web accessibility:

• City and county departments and any contractor building or managing public sites.
• Businesses with a physical presence in San Francisco that offer goods or services to the public.
• State agencies and organisations that receive public funding.

Purely online businesses with no nexus to San Francisco still face risk if they market to or serve customers in the city. When in doubt, treat accessibility as a required part of operations.

Top accessibility issues that trigger complaints

• Missing or poor alt text for images and icons, which prevents screen readers from conveying meaning.
• Insufficient color contrast between text and background, making content unreadable for low-vision users.
• Unlabelled form fields and controls, which break keyboard and assistive-device workflows.
• Inaccessible PDFs and documents without tags, headings or logical reading order.
• Keyboard traps and interactive elements that cannot be reached or used with a keyboard alone.
• Video without captions or audio descriptions when relied on for meaning.
• Misused ARIA attributes that confuse assistive technologies.

Practical step-by-step compliance roadmap for San Francisco websites

This is a prioritised plan that suits most small to mid-size organisations. Treat it as a living process, not a one-off project.

Phase 1 — Discovery and audit

1. Run automated scans for quick coverage. Use two or three reputable tools to find obvious issues.
2. Perform targeted manual testing: keyboard navigation, screen reader walkthroughs, and colour-contrast checks.
3. Inventory non-HTML content such as PDFs, Word files and multimedia. Tag each item by risk and usage frequency.
4. Produce a remediation report that ranks defects by impact, legal risk and effort.

Phase 2 — Remediation priorities

Fix in this order for fastest risk reduction:

• Critical user flows: navigation, account sign-up, checkout and contact forms.
• Images and media that carry meaning: add alt text, captions and transcripts.
• Forms and controls: add labels, error messages and keyboard focus order.
• Documents: convert or tag PDFs and provide accessible alternatives.
• Global issues: proper heading structure, page titles and ARIA corrections.

After the first pass, move to lower-impact items such as decorative image handling, microcopy and performance tuning.

Phase 3 — Policies, statement and monitoring

Create an accessibility policy and publish an accessibility statement that explains your standard, known limitations and contact options. A short template you can adapt:

We aim to make this website accessible to everyone. Our target standard is WCAG 2.1 AA. If you encounter a barrier, contact us at [phone] or [email] and we will provide an accessible alternative and a timeline for repair.

Set up continuous QA: include accessibility checks in your release pipeline, schedule periodic manual audits, and train content authors on accessible practices.

How to handle demand letters and complaints in San Francisco

If you receive a demand letter or a complaint:

• Acknowledge receipt promptly. Record dates and the sender’s requests.
• Start an audit immediately and document your findings.
• Propose a realistic remediation timeline and keep communications factual.
• Retain legal counsel experienced in accessibility if the claim escalates.

Clear records of audits, remediation work and published policies improve your position during negotiations.

Choosing a vendor or tool — quick checklist

• Ask for demonstrable experience with WCAG 2.1 AA remediation and examples.
• Verify they use both automated and manual testing, including screen reader checks.
• Request a clear scope, deliverables and ongoing support options.
• Confirm they provide training for your content authors and developers.
• Insist on a test plan and acceptance criteria tied to WCAG success criteria.

Ongoing maintenance and procurement

Include accessibility requirements in vendor contracts and procurement documents. Require deliverables such as an accessibility conformance report, remediation plan and acceptance testing. Run quarterly or biannual reviews and keep a backlog of accessibility work as part of your product roadmap.

Local resources in San Francisco and California

Useful organisations to contact for guidance include the San Francisco Mayor’s Office on Disability, the California Department of Rehabilitation and federal offices such as the U.S. Department of Justice Civil Rights Division. These offices publish guidance and point to training resources.

Accessibility checklist — quick reference

1. Run automated scans and a manual keyboard and screen reader pass.
2. Fix critical user flows first: navigation, forms and checkout.
3. Add alt text, captions and structured headings.
4. Remediate or replace inaccessible PDFs and documents.
5. Publish an accessibility statement and contact channel.
6. Train staff and add accessibility to procurement rules.
7. Schedule repeat audits and keep remediation logs.

If you want, I can produce a tailored remediation plan for a specific San Francisco website. Tell me the site type, the CMS you use and whether you already ran any accessibility scans.