Los Angeles Website Accessibility WCAG Checklist

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

Overview

In Los Angeles, California, public entities and many businesses must ensure digital services meet recognized accessibility standards such as WCAG to provide equal access. This checklist explains applicable legal frameworks, typical enforcement paths, and concrete technical and administrative steps to align websites and web apps with WCAG 2.1/2.2 best practices. Use this guide to prepare audits, fix barriers, document compliance, and respond to complaints in Los Angeles.

Start with an audit that combines automatic scans and manual, assistive-technology testing.

Legal Standards

Key standards and authorities that apply to websites and digital content used by or provided to the public in Los Angeles include federal accessibility law (Title II of the ADA for public entities and Title III for places of public accommodation), the technical WCAG guidelines (W3C), and applicable state and local building codes for facilities that provide digital kiosks or onsite digital services. Municipal policies for city websites may also set internal compliance timelines and reporting requirements.

Penalties & Enforcement

Enforcement for inaccessible websites affecting Los Angeles residents is commonly pursued under federal ADA enforcement and private litigation; municipal fines specific to website accessibility are generally not specified on municipal pages. Administrative or corrective orders, settlement agreements, and injunctive relief are typical remedies. For physical facilities and kiosks, the Los Angeles Department of Building and Safety (LADBS) enforces building-accessibility standards and related inspection programs LADBS[1]. Federal enforcement and technical guidance are provided by the U.S. Department of Justice (ADA) and related guidance on effective communication and web access ADA.gov[2].

  • Fines and monetary penalties: not specified on the cited page for municipal website enforcement; federal settlements vary by case.
  • Escalation: first compliance orders, negotiated remediation plans, then potential court-ordered injunctive relief or damages if litigation proceeds.
  • Enforcer: LADBS for built-environment access and federal DOJ for ADA matters; city IT or assigned accessibility office enforces internal policies and coordinates remediation.
  • Appeal/review: appeal routes depend on the issuing agency or court; specific time limits are not specified on the cited municipal page.
  • Common violations: missing alt text on images, inadequate contrast, inaccessible forms or keyboard traps, unlabeled controls, and video without captions or transcripts.
If you receive a formal complaint, preserve evidence of remediation steps and communications about accessibility fixes.

Applications & Forms

For physical accessibility inspections or building permits that involve accessible features (for example, kiosks or public terminals), LADBS permit and inspection forms apply; see the LADBS website for current forms and submission instructions LADBS[1]. For web-specific remediation, no single city form is typically required; documentation of audits, remediation plans, and accessibility statements is often requested during enforcement or settlement.

Accessibility Checklist

  • Run automated WCAG 2.1/2.2 checks (a11y linters) and prioritize high-severity issues.
  • Manually test keyboard navigation, focus order, and assistive-technology compatibility.
  • Publish an accessibility statement that lists standards used, known limitations, contact for feedback, and an update cadence.
  • Maintain a remediation plan with deadlines and assigned owners for fixes.
  • Budget for monitoring, training, and user testing with people who have disabilities.

Action Steps

  • Start with a scoped audit covering public-facing pages, transactions, and documents.
  • Record results, publish an accessibility statement, and open a remediation ticket list.
  • Implement fixes in code and content, then retest manually and with users who use assistive technologies.
  • If you operate physical kiosks, submit required permits and schedule LADBS inspections as required.
Accessibility is an ongoing program, not a one-time project.

FAQ

Who enforces website accessibility for city services in Los Angeles?
The city coordinates internal compliance through its IT/accessibility office; physical-access issues are enforced by LADBS and federal ADA enforcement may apply.
What standard should we follow?
WCAG 2.1 level AA is widely used as the technical target; assessors may reference WCAG 2.2 for newer criteria.
Are there municipal fines for inaccessible websites?
Municipal fines specific to websites are not specified on the cited municipal pages; enforcement commonly proceeds via federal ADA actions or settlements.

How-To

  1. Plan: define scope, standards (WCAG level), timeline, and responsible staff.
  2. Audit: run automated tools, perform manual checks, and gather assistive-technology testing.
  3. Remediate: fix code, content, and media; prioritize high-impact barriers.
  4. Verify: retest fixes, perform user testing, and update the accessibility statement.
  5. Respond: set a clear contact for complaints and track resolution timelines.

Key Takeaways

  • Adopt WCAG as the technical baseline and document remediation plans.
  • Combine automated and manual testing with user validation.

Help and Support / Resources