Independent city · Virginia
City of Manassas
42,773 people · Deadline April 26, 2028 · manassasva.gov · 20 pages and a keyboard test, checked October 6, 2026
52out of 100
23critical barriers
Controls a resident can’t use at all. Any one keeps a site at Behind, whatever its score.
Compared
Virginia independent cities of 20,000 to 49,999 people average 76.
Fixing the 23 critical barriers would raise this from 52 (Behind) to 67 (Behind).
See how it does today
Our latest check was on October 6, 2026, and the next is in January 2027. You can check manassasva.gov yourself now, free. You get a report of your own; this page changes at our next check.
Check manassasva.gov now Opens our free check with its address filled in.
What we found
What is wrong and who it affects, most serious first.
-
23
23 buttons have no name, so a blind visitor’s screen reader says just “button”, with no clue to what they do.
- Screen readers
- Voice control
-
106
Text in 106 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
-
21
21 buttons or links are so small, or so close to others, that people with shaky hands may tap the wrong thing.
- Limited hand movement
-
18
18 links have no name, so a blind visitor’s screen reader says just “link”, with no clue to where they go.
- Screen readers
- Voice control
-
8
8 controls show no sign when a keyboard user moves to them, so they can’t tell where they are on the page.
- Keyboard users
- Low vision
-
2
2 items that belong in menus, lists or sets of tabs sit outside them, so screen readers may not announce them as part of their group.
- 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 embedded section, such as a map, video or form from another site, has no title, so a blind visitor’s screen reader can’t say what it is.
- Screen readers
-
1
1 menu, list or set of tabs is built incompletely, so screen readers may announce it without its items or not let a blind visitor move through them.
- Screen readers
More in the full report
The full report is for the city’s own staff. It adds:
- The 20 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 277 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.
- Passed: “Skip to content” works. Keyboard users can jump past the menu.
- Problem: 7 controls show no sign of focus. Keyboard users may not be able to tell where they are.
Questions about this page
Does this mean the city 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 city respond?
Staff with an email address ending in @manassasva.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 City of Manassas?
Claim this page to see where each problem is and what needs to change, set its status for residents, and scan again any day.