Back to reviews and guides

Website ADA Compliance in San Diego: What Businesses Need to Know

This guide explains Website ADA Compliance in San Diego: which standards auditors and courts use, how to run an audit, and a practical remediation checklist. It also covers hiring an auditor and steps to take if you receive a complaint.

Website ADA Compliance in San Diego matters for any business that serves the public. This guide explains which standards courts and auditors use, how to run an audit, practical fixes, and how to hire help locally.

What website accessibility means for San Diego businesses

Federal law requires places of public accommodation to offer equal access. Courts and private claimants commonly use the Web Content Accessibility Guidelines, usually WCAG 2.0 or 2.1 at level AA, as the technical standard. That is the baseline most auditors, vendors, and judges expect.

Who must comply

Businesses open to the public generally must make both their physical and digital services accessible. This includes retail stores, restaurants, hotels, medical clinics, and professional services with customer-facing websites.

There is no single federal web rule. Instead, courts and regulators point to WCAG success criteria and evidence of barriers. State laws have also been used in website access cases.

Common accessibility issues for websites in San Diego

  • Missing or uninformative alt text for images
  • Pages that are not fully usable by keyboard only
  • Poor colour contrast that fails WCAG contrast ratios
  • Forms without correct labels and error messages
  • Inaccessible PDF documents and other attachments
  • Menus and dialogs that do not manage focus or ARIA roles
  • Video without captions or transcripts

Quick, practical accessibility checklist

  • Provide meaningful alt text and decorative-image nulls (alt=“”).
  • Ensure every interactive element is reachable and operable with keyboard.
  • Meet WCAG contrast ratios for text and controls.
  • Label form fields and show clear, programmatic error messages.
  • Offer captions for video and text alternatives for complex images.
  • Use semantic HTML headings and landmarks for navigation.
  • Check PDFs and other documents for accessibility or provide HTML alternatives.
  • Publish an accessibility statement with contact information and a remediation plan.

How to run a practical accessibility audit

Combine automated scans with manual testing. Automated tools catch many issues but miss keyboard and screen reader problems. Manual tests find real-world barriers users face.

Step-by-step audit

  1. Run automated scans with Axe, WAVE, and Lighthouse to flag common violations.
  2. Do keyboard-only testing across critical user journeys: navigation, search, checkout, contact forms.
  3. Test with a screen reader such as NVDA (Windows) or VoiceOver (macOS) on key pages.
  4. Check colour contrast with a contrast tool and inspect semantic heading order.
  5. Review PDFs and attachments for accessibility or provide accessible HTML versions.
  6. Document issues, severity, and recommended fixes; include code examples when possible.

Prioritise fixes

Start with barriers that block access: keyboard inoperability, missing form labels, and essential content hidden from assistive tech. Then address medium-impact items such as contrast and non-critical ARIA. Finally, tidy low-impact issues like decorative markup.

Remediation process and ongoing maintenance

Fixes follow a sequence: discovery, prioritisation, remediation, quality assurance, and monitoring. Include the website owner, developers, and somebody who knows assistive technology in QA.

Deliverables a remediation project should produce

  • A prioritized issue list mapped to WCAG success criteria
  • Code-level guidance or pull requests for developers
  • Regression test scripts and acceptance criteria
  • An accessibility statement and feedback channel
  • Training for content editors and developers

Table: Common issues and how to fix them

Issue How to fix
Images without alt Add succinct alt text or alt=“” for decorative images
Keyboard traps Ensure all modal dialogs move focus and allow exit via keyboard
Low contrast Meet WCAG contrast ratios for text and UI elements
Unlabelled form fields Use label elements and aria-describedby for help text

Common mistakes San Diego businesses make

  • Relying only on automated tools and ignoring manual tests.
  • Fixing isolated pages without addressing templates or CMS patterns.
  • Publishing inaccessible documents after the site is fixed.
  • Not training content editors, which causes regressions.
  • Thinking accessibility is a one-time project rather than a process.

How to choose an accessibility vendor or auditor

Ask for sample reports that map issues to WCAG and show code examples. Confirm they perform manual testing with screen readers and keyboard only. Get references and ask for a clear remediation plan and ongoing monitoring options.

Questions to ask potential vendors

  • Do you map every finding to a WCAG success criterion?
  • Which assistive technologies do you test with?
  • Will you provide developer-ready fixes or only a report?
  • Do you offer training for content teams and a maintenance plan?
  • Can you show local references or similar projects in my sector?

What to do if you get a demand letter or complaint

Do not ignore a notice. Preserve relevant records and consult an attorney experienced with accessibility claims. At the same time, prepare a remediation plan with clear milestones and share it with your counsel. Fixing the site promptly and documenting actions can affect how a dispute is resolved.

Local considerations for San Diego businesses

San Diego companies should balance legal risk with customer experience. Accessibility improves reach and reduces the chance of a claim. Work with vendors who understand US federal law and California legal context and who can test on the devices your customers use in the region.

Free tools and testing approaches to get started

  • Automated scanners: Axe, WAVE, Lighthouse
  • Screen readers: NVDA on Windows, VoiceOver on macOS and iOS
  • Keyboard-only navigation for key user journeys
  • Contrast checkers and manual code inspection

Next steps

Start with a short audit of priority pages: home, contact, product or service pages, and any checkout or booking flows. Create a one-page remediation plan and assign owners. Track fixes, retest, and publish an accessibility statement with a contact method.

If you need help, look for auditors who provide both technical fixes and training so accessibility becomes part of how your team works.