WCAG Website Accessibility Requirements - St. Petersburg

St. Petersburg, Florida requires public-facing digital services to follow recognized accessibility standards and provides an official accessibility statement and compliance guidance on the city website^[1]. This article summarizes the applicable expectations for city departments, contractors, and website vendors, identifies the enforcement and complaint paths, and outlines practical steps to meet WCAG requirements under local practice and the city code where relevant^[2]. It is aimed at city staff, vendors, and local businesses that provide services to the public through web pages or web applications.

Scope and What WCAG Means for St. Petersburg

In practice, WCAG provides technical criteria for perceivable, operable, understandable, and robust web content. For entities operating within St. Petersburg, this typically covers:

• City-owned websites and web applications.
• Third-party contractors delivering public services or digital content on behalf of the city.
• Public documents and interactive services required to be accessible when published online.

Where the city has formal procurement or contract language, WCAG conformance requirements are enforced through contracting and vendor management rather than by a standalone ordinance in most cases. For the controlling municipal code language and administrative rules, consult the city code and official accessibility pages^[2].

Penalties & Enforcement

Enforcement of web accessibility for city services is typically administrative and contractual. Specific monetary fines or statutory penalties for web accessibility failures are not generally set out in a separate municipal ordinance; where the code is silent, remedies are handled through administrative corrective orders, procurement remedies, or civil claims. See the cited city resources for the controlling statements and procedures^[2].

• Fines or monetary penalties: not specified on the cited page.
• Escalation: first notice, corrective period, and possible contract sanctions for repeat failures; exact escalation steps not specified on the cited page.
• Non-monetary sanctions: corrective orders, mandated remediation, withholding of payment under city contracts, and removal of noncompliant content.
• Enforcer: responsible department or contract administrator (typically the city IT/website team, procurement, or ADA coordinator) and formal complaint intake via the city accessibility or customer service pages.
• Inspection and complaint pathways: submission of accessibility complaints to the city using the official contact or ADA complaint form where provided.
• Appeals/review: procedural review or appeal processes are handled through administrative review, procurement protest, or civil court; specific time limits for appeals are not specified on the cited page.

Applications & Forms

The city does not publish a standalone municipal "WCAG permit." Where a formal form exists, it will be listed on the city accessibility or departmental pages; if no form is published, remediation is usually requested via the city's accessibility contact or procurement administrator. Specific forms and fees: not specified on the cited page.

Common Violations and Typical Outcomes

• Missing alt text on images — corrective order to remediate.
• Poor keyboard navigation — requirement to fix interactive components.
• Uncaptioned multimedia — request to add captions or transcripts.
• Inaccessible PDFs and documents — direction to provide accessible versions.

How to Comply - Practical Steps

Follow a documented remediation workflow to reduce legal and operational risk:

1. Inventory all public web pages and digital services.
2. Run automated and manual WCAG tests and document failures.
3. Prioritize fixes for high-use and critical public services, then remediate.
4. Adopt procurement clauses requiring WCAG conformance for new contracts.
5. Provide clear contact information for accessibility feedback and response timelines.

FAQ

Does St. Petersburg require WCAG compliance for city websites?

The city's public accessibility statement and administrative guidance indicate the city expects accessibility for public web services; consult the official accessibility page for the exact language and scope.^[1]

Who should I contact to report an inaccessible city page?

Report accessibility issues through the city's official accessibility contact or ADA coordinator listed on the city website; departmental contacts may handle specific service areas.

Are there fines for noncompliant websites?

Monetary fines specific to web accessibility are not specified on the cited municipal pages; remedies are typically administrative or contractual.^[2]

How-To

1. Assign an accessibility coordinator for the website and gather stakeholder approval.
2. Perform a full accessibility audit using automated tools and manual testing with assistive technologies.
3. Create a remediation plan with prioritized issues, owners, and deadlines.
4. Implement fixes, update documentation, and train content editors on accessible publishing.
5. Publish an accessibility statement and a feedback/reporting mechanism on the site.

Key Takeaways

• St. Petersburg publishes an accessibility statement and administrative guidance for web services.^[1]
• Enforcement is primarily administrative and contractual; specific fines are not listed on the cited pages.^[2]

Help and Support / Resources

• St. Petersburg - Accessibility statement and contact
• City of St. Petersburg Code of Ordinances (Municode)
• St. Petersburg Planning & Building Department
• City IT / web services and procurement contacts

1. [1] City of St. Petersburg - Accessibility statement and contact
2. [2] City of St. Petersburg Code of Ordinances (Municode)