Accessible Indexpowered by Dynamosys

Town · Caroline County, Maryland

Town of Greensboro

1,916 people · Deadline April 26, 2028 · greensboromd.org · 20 pages and a keyboard test, checked November 2, 2026

Status

Scanned

From our checks · November 2026

Not yet claimed by its staff

What the statuses mean

75out of 100

ScoreAlmost readyA few problems found, none a critical barrierAutomated checks of 20 pages, November 2, 2026. They find many problems, not all.

0critical barriers

The automated checks found no control a resident can’t use at all.

Compared

Maryland towns of 0 to 1,999 people average 70.

See how it does today

Our latest check was on November 2, 2026, and the next is in January 2027. You can check greensboromd.org yourself now, free. You get a report of your own; this page changes at our next check.

Check greensboromd.org now Opens our free check with its address filled in.

What we found

What is wrong and who it affects, most serious first.

  • 21

    21 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
  • 13

    13 images have no description, so a blind visitor’s screen reader says only “image” or reads out file names.

    • Screen readers
  • 4

    4 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
  • 2

    2 pages have 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

    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.

    Not in the score
    • Keyboard users
    • Screen readers

More in the full report

The full report is for the town’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

Claim this page to see it

The keyboard test

We pressed Tab 76 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.
  • 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 @greensboromd.org 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 Greensboro?

Claim this page to see where each problem is and what needs to change, set its status for residents, and scan again any day.

An address ending in @greensboromd.org, the domain of the website we check. We’ll email you a link to confirm.

Read the Terms and our Privacy policy.

Our commitments to governments

This is an automated scan. It finds many but not all accessibility problems, and it can be wrong. If something looks off, let us know. This is not legal advice or a certification of compliance.