Town · Prince George's County, Maryland
Town of Brentwood
3,824 people · Deadline April 26, 2028 · brentwoodmd.gov · 12 pages and a keyboard test, checked November 2, 2026
68out of 100
0critical barriers
The automated checks found no control a resident can’t use at all.
Compared
Maryland towns of 2,000 to 4,999 people average 68.
See how it does today
Our latest check was on November 2, 2026, and the next is in January 2027. You can check brentwoodmd.gov yourself now, free. You get a report of your own; this page changes at our next check.
Check brentwoodmd.gov now Opens our free check with its address filled in.
What we found
What is wrong and who it affects, most serious first.
-
46
Text in 46 places is too faint against its background, so people with low vision, or anyone reading a phone in sunlight, may struggle to read it.
- Low vision
- Color blindness
-
9
Text in 9 places has fixed spacing, so people with dyslexia or low vision who widen the spacing to read more easily can’t.
- Low vision
- Cognitive
-
6
6 parts of the page are hidden from screen readers but can still be reached with the Tab key, so a blind visitor lands on things their screen reader won’t describe.
- Screen readers
- Keyboard users
-
6
6 buttons or links are so small, or so close to others, that people with shaky hands may tap the wrong thing.
- Limited hand movement
-
2
2 embedded sections, such as maps, videos or forms from other sites, have no title, so a blind visitor’s screen reader can’t say what they are.
- Screen readers
-
1
On 1 page, pressing Tab gets stuck on one control, so someone using a keyboard instead of a mouse can’t reach the rest of the page.
- Keyboard users
- Screen readers
-
1
1 page has to be scrolled sideways on a narrow phone screen, so people who enlarge text must scroll back and forth to read each line.
- Low vision
-
1
1 control shows no sign when a keyboard user moves to it, so they can’t tell where they are on the page.
- Keyboard users
- Low vision
-
1
1 link has no name, so a blind visitor’s screen reader says just “link”, with no clue to where it goes.
- Screen readers
- Voice control
More in the full report
The full report is for the town’s own staff. It adds:
- The 12 pages we checked, by name
- Where each problem is, with a screenshot
- What needs to change, in the order to fix it
- A new check any day, once something is fixed
The keyboard test
We pressed Tab 43 times through the homepage, as someone who can’t use a mouse would. What it found is shown here and is not yet counted in the score.
- Problem: Focus gets stuck. Pressing Tab stops on one control, so keyboard users can’t reach the rest of the homepage.
- Passed: “Skip to content” works. Keyboard users can jump past the menu.
- Passed: Focus can be seen. Every control we reached shows where the keyboard is.
Questions about this page
Does this mean the town is breaking the law?
No. This is an automated check against WCAG 2.1 AA, the standard the ADA Title II rule sets for state and local governments. Automated checks find many problems but not all, and only a full review can say whether a site meets the rule.
How often is this page updated?
Every three months, in January, April, July and October. Once its staff claim this page, they can also scan the site again, once a day; the new result shows here like our regular check, marked as checked at their request. The date at the top shows the latest check, and the score can go up as problems are fixed.
How can the town respond?
Staff with an email address ending in @brentwoodmd.gov can claim this page to set its status for residents, see where each problem is, and scan the site again. Think a result is wrong? Tell us and we will check it again.
Work for the Town of Brentwood?
Claim this page to see where each problem is and what needs to change, set its status for residents, and scan again any day.