Baltimore City WCAG Accessibility Rules for Websites
Baltimore, Maryland requires city web properties to follow recognized accessibility standards to ensure information and services are usable by people with disabilities. This guide explains the city policy baseline, how compliance is enforced, common violations, practical steps for web teams, and how members of the public can report barriers. It summarizes official Baltimore resources, the office responsible for oversight, and where to find forms or file complaints. Use this as a practical checklist for municipal web managers and advocates seeking remedies.
Scope and Standard
The City of Baltimore's digital accessibility policy adopts the Web Content Accessibility Guidelines (WCAG) as the technical standard for city websites and web-based applications. Compliance expectations cover content, navigation, and interactive elements, aligned to WCAG Level AA where specified by policy.[1]
Who enforces accessibility
- Primary oversight: Baltimore City Department of Information Technology (or designated digital accessibility officer).[1]
- Complaints and reporting are routed through the city accessibility/reporting portal or 311 channels; technical remediation is coordinated with the owning department.[2]
Penalties & Enforcement
The city's published digital accessibility policy emphasizes remediation and corrective action rather than specifying civil fines in the policy text. Where monetary penalties or formal sanctions are applicable, the city refers to applicable laws and administrative processes; specific fine amounts and escalation steps are not specified on the cited policy page.[1]
- Fine amounts: not specified on the cited page.[1]
- Escalation (first/repeat/continuing offenses): not specified on the cited page; policy emphasizes correction timelines determined case by case.[1]
- Non-monetary sanctions: orders to remediate content, removal or temporary disablement of noncompliant features, and referral to legal or procurement remedies are possible per department procedures (details not specified on the cited page).[1]
- Enforcer: Department of Information Technology or the city accessibility officer; complaints filed via the official reporting link or 311 trigger review.[2]
- Inspection and complaint pathway: submit a report through the official accessibility/reporting page or contact 311 for intake; the city documents receipt and assigns remediation tasks.[2]
- Appeal/review routes and time limits: the cited policy describes remediation and coordination steps but does not specify a judicial or administrative appeal timeline; citizens may pursue administrative review or external legal remedies under federal/state law where applicable (time limits not specified on the cited page).[1]
Applications & Forms
The city's digital accessibility policy links to reporting and accommodation request procedures; there is no separate universal "accessibility permit" form published on the main policy page. For technical remediation requests or accommodation submissions, use the city reporting portal or contact channels cited below.[2]
Common violations and typical remedies
- Missing alt text for images — remedy: add descriptive alt attributes and update content management processes.
- Non-keyboard interactive controls — remedy: implement keyboard focus and ARIA roles.
- Poor color contrast — remedy: update styles to meet WCAG contrast ratios.
- PDFs or documents not accessible — remedy: provide accessible versions or HTML alternatives.
Action steps for web teams
- Conduct a WCAG 2.1 AA audit and prioritize fixes based on user impact.
- Create a remediation timeline and publish an accessibility statement with contact information.
- Train content authors on accessible authoring and include accessibility checks in releases.
- Provide a clear reporting route for users and track responses until resolution.
FAQ
- Are Baltimore city websites required to meet WCAG?
- Yes. City policy adopts WCAG as the technical standard for city-managed web properties; see the city accessibility policy for scope and exceptions.[1]
- How do I report an accessibility problem?
- Report issues through the city's official accessibility reporting portal or by contacting 311; provide URL, device/browser, and a description of the barrier.[2]
- What remedies are available if the city does not fix a barrier?
- If internal remediation does not resolve the issue, complainants may seek external legal remedies under federal and state disability laws; the policy focuses on remediation before enforcement actions, and specific penalties are not listed on the policy page.[1]
How-To
- Collect details: note the page URL, device, browser, time, and describe the accessibility barrier.
- Submit a report via the city's accessibility reporting page or call 311 to log the issue.
- Request a timeline and reference number; follow up with the department if you do not receive acknowledgment.
- If unresolved, request administrative review or consult federal/state enforcement options for disability discrimination.
Key Takeaways
- Baltimore adopts WCAG as the standard and focuses on remediation through departmental action.
- Report barriers via the official portal or 311 and request a response and timeline.
Help and Support / Resources
- Baltimore City Department of Information Technology
- City reporting and service request portal
- Baltimore City Council and municipal code resources
- 311 Baltimore