Skip to main content

Public reports › Cities & towns · Michigan

City · Michigan · population 21,813

City of Birmingham

bhamgov.org · homepage scanned Oct 15, 2026 · WCAG 2.2 A/AA automated check

A

Accessibility score

94/100 · Excellent

The homepage passed every automated WCAG 2.2 A/AA check we run. That removes the common, machine-detectable barriers; it does not mean every page or every manual criterion passes.

0

Critical

1

Major

0

Minor

Screenshot of the City of Birmingham homepage at scan time

Homepage as loaded by our crawler on Oct 15, 2026.

In plain English

What this means for visitors

The scan found one major issue on the website, which is that the page language is not declared. This means that screen readers, used by visitors who are blind or have low vision, may not read the content correctly. To improve accessibility, declaring the page language should be fixed first. Automated scans like this one catch many issues, but not all, so further review is recommended to ensure accessibility for all visitors under ADA Title II.

Findings

1 issue type found on the homepage

Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.

#1MajorWCAG 3.1.11 elementRule details ↗

Page language is not declared

Screen readers don't know which language to pronounce the page in, so it may read English with a wrong accent or mispronounce everything.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Add lang="en" to the <html> tag. Most CMS themes have this in the site settings or header template.

Severity guide

How to read the counts

Critical

Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).

Major

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

Minor

Reduces clarity or consistency (heading order, landmarks, touch-target size).

What this grade does and does not cover

  • Covers: the public homepage only, loaded once in a desktop browser, tested with axe-core against WCAG 2.2 Level A and AA rules (a superset of the WCAG 2.1 AA standard in the DOJ rule).
  • Does not cover: inner pages, PDFs and documents, logged-in portals, video captions, alt-text quality, keyboard usability of custom widgets, or anything that needs a human judgment.
  • A grade is a monitoring signal, not a legal assessment or certification. How we score.