Website Accessibility Rules for Vendors in Pasadena

Technology and Data California 3 Minutes Read · published February 21, 2026 Flag of California

Pasadena, California requires that vendors who supply websites, web applications, or digital services to the city and to the public follow recognized accessibility standards and procurement requirements. This guide explains how vendors can align with WCAG expectations, where the city documents accessibility obligations, how to respond to complaints, and practical steps for contracts, testing, and remediation. It is intended for vendors, contractors, and nonprofit partners who provide digital services for the City of Pasadena or interact with city-managed public portals.

Scope and Standards

Vendors should design and deliver websites and digital content that meet modern accessibility criteria—typically WCAG 2.1 Level AA or later as required by procuring departments—and ensure compatibility with assistive technologies. For official city guidance and the accessibility statement, consult the city’s accessibility information and vendor procurement pages City accessibility statement[1] and Purchasing and contracting[2].

Check contract documents for the exact WCAG version required for each engagement.

Penalties & Enforcement

Enforcement for web accessibility obligations related to city contracts is handled through the contracting department and the city office responsible for digital services or IT; where violations involve access to public services there may also be administrative or legal remedies. Specific monetary fines and escalation schedules are not listed on the cited city procurement and accessibility pages and therefore are not specified here; vendors should review contract language and department directives for contract-specific sanctions Purchasing and contracting[2].

  • Fines: not specified on the cited page.
  • Escalation: first/repeat/continuing offence details are not specified on the cited page.
  • Non-monetary sanctions: remedial orders, contract breach determinations, withheld payments, or termination are typical administrative options identified in contracting practice; specific measures appear in individual contracts.
  • Enforcer and complaint pathway: Contracting/Purchasing and the city IT or communications office receive accessibility concerns; use the city accessibility contact and procurement contacts on the official pages to submit complaints City accessibility statement[1].
  • Appeals/review: procedures and time limits for appeals or protest of contracting decisions are governed by procurement rules or contract dispute clauses and are not specified on the cited accessibility page.
  • Defences/discretion: contracting officers may consider documented remediation plans, good-faith efforts, or approved variances; check contract terms for accommodations.
If a contract requires WCAG conformance, attach test reports and remediation timelines to avoid penalties.

Applications & Forms

The city publishes procurement registration and vendor forms via the Purchasing Division; accessibility-specific compliance forms or checklists may be referenced inside contract documents. If a distinct accessibility compliance form is required it will be identified in the solicitation or contract. The city accessibility page does not list a universal accessibility submission form and therefore specific form names, numbers, fees, and deadlines are not specified on the cited page City accessibility statement[1].

How vendors should comply

  • Conduct an accessibility audit against the WCAG version required by the contract.
  • Remediate issues in priority order: content, forms, navigation, and PDF/documents.
  • Include accessibility clauses, acceptance tests, and remediation timelines in bids and statements of work.
  • Maintain testing records and provide assistive-technology compatibility evidence during acceptance review.
  • Schedule periodic re-testing and update accessibility attestations when content or platforms change.

FAQ

Who enforces website accessibility for city contracts?
The City’s Purchasing/Contracting division together with the department that manages the service (often IT or Communications) enforces accessibility requirements; report concerns via the city accessibility and procurement contact pages.[1][2]
What WCAG level does Pasadena require?
WCAG level required is specified in each solicitation or contract; check the contract documents. The city accessibility page outlines the city’s commitment to accessible digital services but does not state a single, universal WCAG version for all contracts.[1]
How do I report an inaccessible city web page?
Use the contact or accessibility feedback mechanism listed on the City of Pasadena accessibility page to submit a complaint or request assistance; include URL, expected behaviour, and screenshots where possible.[1]

How-To

  1. Identify the WCAG version or accessibility standard named in the solicitation or contract.
  2. Run a full automated scan and a manual audit with assistive technologies.
  3. Produce a remediation plan with priorities, estimated hours, and target dates.
  4. Deliver test reports and evidence as part of acceptance; update documentation on changes.
  5. Respond to accessibility complaints promptly and provide status updates to the contracting officer.

Key Takeaways

  • Check contract language for the exact WCAG level and acceptance tests.
  • Keep audit records and remediation timelines in your contract files.
  • Report accessibility issues using the city’s official accessibility contact channels.

Help and Support / Resources


  1. [1] City of Pasadena accessibility information and contact page
  2. [2] City of Pasadena Purchasing Division and contractor resources