Shreveport Website Accessibility - WCAG Steps
Introduction
This guide explains practical steps for achieving WCAG website accessibility in Shreveport, Louisiana, tailored for municipal IT teams, contractors, and department managers. It summarizes key actions to audit, remediate, document, and maintain accessible digital services; explains who enforces accessibility at the city level and how complaints or requests for accommodation move through municipal channels; and offers concrete next steps for development, procurement, and communications. The guidance is practical and focused on compliance workflows rather than technical deep dives, and is current as of February 2026.
Core WCAG Compliance Steps for Shreveport IT
Follow a repeatable program lifecycle: assess, prioritize, remediate, verify, publish, and monitor. Align technical fixes to WCAG 2.1 AA (or the version the city adopts) and coordinate with legal, communications, and procurement.
- Conduct an initial accessibility audit (automated scans + manual testing by users with disabilities).
- Prioritize issues by impact and user journeys, set sprint targets and deadlines for remediation.
- Remediate templates, components, and legacy pages; fix semantic HTML, ARIA, keyboard focus, and color contrast.
- Perform manual verification with assistive technologies and user testing before publishing fixes.
- Publish an accessibility statement describing conformance level, known issues, contact info, and a remediation timeline.
- Include accessibility requirements and acceptance tests in RFPs, contracts, and service-level agreements.
Penalties & Enforcement
Shreveport’s municipal code and the city web pages reviewed do not set a city-specific fine schedule for website accessibility; details of monetary penalties are not specified on the cited pages. Enforcement in practice commonly follows complaint-driven paths: local complaint to the city ADA coordinator or department, administrative resolution, or escalation to state or federal enforcement (for example, under federal ADA Title II). The city department responsible for handling access complaints is typically the municipal ADA coordinator or Human Resources/Legal department; refer to official city contact pages in "Help and Support / Resources" below. Where the local code does not specify penalties, federal remedies or court actions may apply; the exact local escalation steps and fine amounts are not specified on the cited municipal pages.
- Fine amounts: not specified on the cited pages.
- Escalation: first complaint, administrative review, possible referral to state or federal agencies; specific timelines not specified on the cited pages.
- Non-monetary sanctions: corrective orders, mandated remediation plans, or court injunctions where applicable.
- Enforcer/contact: City ADA coordinator or Human Resources/Legal (see Resources section for official contacts).
- Appeals/review: appeal routes may include administrative review and judicial remedies; specific local time limits are not specified on the cited pages.
- Defences/discretion: documented good-faith remediation plans, granted variances, or proven undue burden financial defenses where applicable; city-specific rules not specified on the cited pages.
Applications & Forms
No city-specific WCAG compliance application form or permit was published on the primary municipal pages reviewed; the official pages reviewed do not list a dedicated web-accessibility compliance form. Departments commonly accept ADA grievance submissions, accommodation requests, or procurement compliance evidence through standard HR, Legal, or Purchasing forms—check the city contacts in Resources for the proper submission route.
Operational Steps and Roles
Implement clear responsibilities and records: IT fixes, procurement clauses, communications publishing, accessibility statement ownership, and a remediation tracker. Keep versioned evidence of testing and user reports.
- Procurement: include explicit WCAG/Section 508 clauses and acceptance tests in contracts.
- Documentation: maintain test reports, remediation tickets, and accessibility statements publicly.
- Monitoring: schedule periodic re-audits and incorporate accessibility in sprint definitions.
FAQ
- What standard should Shreveport municipal websites meet?
- Most municipal guidance recommends WCAG 2.1 AA or the version the city formally adopts; check the city’s published policy or procurement language for the definitive standard.
- How do I report an accessibility problem on a city site?
- Report to the City ADA coordinator or the department responsible for the service; the city’s official contact pages list the preferred complaint and accommodation routes.
- Does the city publish timelines for fixing accessibility defects?
- Timelines vary by issue severity and resources; if no timeline is published, request a remediation plan from the responsible department.
How-To
- Run an initial automated scan and document high-priority accessibility failures.
- Perform manual testing on representative pages and key user journeys using assistive technologies.
- Implement fixes in a staging environment, focusing on templates and components shared across pages.
- Verify remediation with manual tests and update the public accessibility statement to reflect changes.
- Document evidence, add accessibility acceptance tests to procurement and deployment checklists, and schedule recurring audits.
Key Takeaways
- Start with a combined automated and manual audit and publish an accessibility statement.
- Include WCAG requirements in contracts and make remediation part of normal release cycles.
Help and Support / Resources
- City of Shreveport Code of Ordinances (Municode)
- City of Shreveport - Human Resources / ADA contacts
- Louisiana Department of Administration - Office of Information Services