Skip to main content
← Read the reportResearch

Florida county website accessibility, county by county

What our automated WCAG 2.1 AA test found on the home page of each Florida county government website on October 14, 2026. We tested 64 of the 67; 3 turned our browser away.

These are automated results for one page, not an audit, and sites change, so a page may look different today. “Place” means one element on the page that failed a check. The report explains the method. If you see a mistake, email hello@awesomecause.com.

1 check failed

Alachua County

Home page tested: alachuacounty.us · 1 failure in total

  • Definition lists built with the wrong markup WCAG 1.3.1 · 1 place
Overlay widget
None found
Not tested

Baker County

bakercountyfl.org turned our automated browser away (status 403), so we have no results. We did not try to get around the block.

No detectable failures

Bay County

Home page tested: baycountyfl.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
UserWay
Accessibility link
None found on the home page
2 checks failed

Bradford County

Home page tested: bradfordcountyfl.gov · 3 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
UserWay
Accessibility link
None found on the home page
No detectable failures

Brevard County

Home page tested: brevardfl.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
Yes, to brevardfl.gov/Accessibility
4 checks failed

Broward County

Home page tested: broward.org · 30 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 19 places
  • ARIA roles outside the parent they require WCAG 1.3.1 · 8 places
  • Hidden content that keyboard focus can still land on WCAG 4.1.2 · 2 places
  • ARIA roles missing the children they require WCAG 1.3.1 · 1 place
Overlay widget
UserWay
Accessibility link
Yes, to broward.org/Terms
Not tested

Calhoun County

calhouncountyfl.org turned our automated browser away (status 403), so we have no results. We did not try to get around the block.

4 checks failed

Charlotte County

Home page tested: charlottecountyfl.gov · 20 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 10 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 6 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 3 places
  • Images with no text alternative WCAG 1.1.1 · 1 place
Overlay widget
UserWay
Accessibility link
None found on the home page
6 checks failed

Citrus County

Home page tested: citruscounty.gov · 23 failures in total

  • Hidden content that keyboard focus can still land on WCAG 4.1.2 · 9 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 5 places
  • Text with too little contrast against its background WCAG 1.4.3 · 4 places
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 2 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
  • Lists built with the wrong markup WCAG 1.3.1 · 1 place
Overlay widget
UserWay
2 checks failed

Clay County

Home page tested: claycountygov.com · 9 failures in total

  • List items that aren’t inside a list WCAG 1.3.1 · 7 places
  • Lists built with the wrong markup WCAG 1.3.1 · 2 places
Overlay widget
UserWay
No detectable failures

Collier County

Home page tested: collier.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
No detectable failures

Columbia County

Home page tested: columbiacountyfla.com

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
None found on the home page
1 check failed

DeSoto County

Home page tested: desotobocc.com · 1 failure in total

  • Embedded frames (maps, video, widgets) with no title WCAG 4.1.2 · 1 place
Overlay widget
Accessibility Enabled / Monsido
Accessibility link
Yes, to desotobocc.com/accessibility
4 checks failed

Dixie County

Home page tested: dixiecounty.us · 22 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 15 places
  • Links that only color sets apart from the text around them WCAG 1.4.1 · 3 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 3 places
  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 1 place
Overlay widget
accessiBe
No detectable failures

Duval County (Consolidated with the City of Jacksonville)

Home page tested: jacksonville.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
Yes, to jacksonville.gov/accessibility
1 check failed

Escambia County

Home page tested: myescambia.com · 2 failures in total

  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 2 places
Overlay widget
UserWay
No detectable failures

Flagler County

Home page tested: flaglercounty.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
accessiBe
No detectable failures

Franklin County

Home page tested: franklincountyflorida.com

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
2 checks failed

Gadsden County

Home page tested: gadsdencountyfl.gov · 6 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 5 places
  • Embedded frames (maps, video, widgets) with no title WCAG 4.1.2 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
7 checks failed

Gilchrist County

Home page tested: gilchrist.fl.us · 7 failures in total

  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 1 place
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 1 place
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 1 place
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
  • Embedded frames (maps, video, widgets) with no title WCAG 4.1.2 · 1 place
  • Images with no text alternative WCAG 1.1.1 · 1 place
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
UserWay
Accessibility link
Yes, to gilchrist.fl.us/accessibility
3 checks failed

Glades County

Home page tested: myglades.com · 7 failures in total

  • Lists built with the wrong markup WCAG 1.3.1 · 3 places
  • List items that aren’t inside a list WCAG 1.3.1 · 3 places
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
UserWay
2 checks failed

Gulf County

Home page tested: gulfcounty-fl.gov · 3 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
1 check failed

Hamilton County

Home page tested: hamiltoncountyfl.com · 2 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
Overlay widget
UserWay
Accessibility link
None found on the home page
Not tested

Hardee County

hardeecountyfl.gov turned our automated browser away (status 403), so we have no results. We did not try to get around the block.

3 checks failed

Hendry County

Home page tested: hendryfla.net · 160 failures in total

  • Hidden content that keyboard focus can still land on WCAG 4.1.2 · 142 places
  • Text with too little contrast against its background WCAG 1.4.3 · 17 places
  • Images with no text alternative WCAG 1.1.1 · 1 place
Overlay widget
None found
1 check failed

Hernando County

Home page tested: hernandocounty.us · 2 failures in total

  • Graphics marked as images with no text alternative WCAG 1.1.1 · 2 places
Overlay widget
UserWay
3 checks failed

Highlands County

Home page tested: hcbcc.net · 27 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 16 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 8 places
  • Hidden content that keyboard focus can still land on WCAG 4.1.2 · 3 places
Overlay widget
UserWay
1 check failed

Hillsborough County

Home page tested: hcfl.gov · 18 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 18 places
Overlay widget
UserWay
1 check failed

Holmes County

Home page tested: holmescountyfla.com · 2 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
Overlay widget
UserWay
Accessibility link
Yes, to holmescountyfla.com/accessibility
No detectable failures

Indian River County

Home page tested: indianriver.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
UserWay
Accessibility link
None found on the home page
4 checks failed

Jackson County

Home page tested: jacksoncountyfl.gov · 9 failures in total

  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 6 places
  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 1 place
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 1 place
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
None found
1 check failed

Jefferson County

Home page tested: jeffersoncountyfl.gov · 1 failure in total

  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
None found
1 check failed

Lafayette County

Home page tested: lafayettecountyfl.org · 1 failure in total

  • ARIA buttons, links or menu items with no name WCAG 4.1.2 · 1 place
Overlay widget
None found
1 check failed

Lake County

Home page tested: lakecountyfl.gov · 1 failure in total

  • ARIA attributes with values that aren’t valid WCAG 4.1.2 · 1 place
Overlay widget
AudioEye
Accessibility link
Yes, to lakecountyfl.gov/site/accessibility
3 checks failed

Lee County

Home page tested: leegov.com · 4 failures in total

  • Controls nested inside other controls WCAG 4.1.2 · 2 places
  • Form fields with no label WCAG 4.1.2 · 1 place
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
No detectable failures

Leon County

Home page tested: cms.leoncountyfl.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
Yes, to cms.leoncountyfl.gov/Accessibility
1 check failed

Levy County

Home page tested: levycounty.org · 2 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
Overlay widget
AudioEye
Accessibility link
Yes, to levycounty.org/accessibility
2 checks failed

Liberty County

Home page tested: libertycountyfl.org · 2 failures in total

  • ARIA roles missing an attribute they require WCAG 4.1.2 · 1 place
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
accessiBe
5 checks failed

Madison County

Home page tested: madisoncountyfl.com · 7 failures in total

  • Graphics marked as images with no text alternative WCAG 1.1.1 · 3 places
  • ARIA buttons, links or menu items with no name WCAG 4.1.2 · 1 place
  • ARIA roles missing an attribute they require WCAG 4.1.2 · 1 place
  • Images with no text alternative WCAG 1.1.1 · 1 place
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
None found
2 checks failed

Manatee County

Home page tested: mymanatee.org · 2 failures in total

  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 1 place
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
None found
4 checks failed

Marion County

Home page tested: marionfl.org · 19 failures in total

  • Images with no text alternative WCAG 1.1.1 · 8 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 6 places
  • Lists built with the wrong markup WCAG 1.3.1 · 3 places
  • ARIA roles outside the parent they require WCAG 1.3.1 · 2 places
Overlay widget
UserWay
Accessibility link
Yes, to marionfl.org/our-county/accessibility
No detectable failures

Martin County

Home page tested: martin.fl.us

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
Yes, to martin.fl.us/accessibility-feedback
4 checks failed

Miami-Dade County

Home page tested: miamidade.gov · 10 failures in total

  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 3 places
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 3 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 3 places
  • Page language not set WCAG 3.1.1 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
4 checks failed

Monroe County

Home page tested: monroecounty-fl.gov · 13 failures in total

  • ARIA attributes with values that aren’t valid WCAG 4.1.2 · 5 places
  • Lists built with the wrong markup WCAG 1.3.1 · 5 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
  • Embedded frames (maps, video, widgets) with no title WCAG 4.1.2 · 1 place
Overlay widget
None found
Accessibility link
Yes, to monroecounty-fl.gov/1033
3 checks failed

Nassau County

Home page tested: nassaucountyfl.com · 3 failures in total

  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 1 place
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 1 place
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 1 place
Overlay widget
None found
Accessibility link
Yes, to nassaucountyfl.com/1378
6 checks failed

Okaloosa County

Home page tested: myokaloosa.com · 34 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 13 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 13 places
  • ARIA attributes the element’s role doesn’t support WCAG 4.1.2 · 2 places
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 2 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 2 places
  • Embedded frames (maps, video, widgets) with no title WCAG 4.1.2 · 2 places
Overlay widget
None found
2 checks failed

Okeechobee County

Home page tested: okeechobeecountyfl.gov · 4 failures in total

  • ARIA roles outside the parent they require WCAG 1.3.1 · 2 places
  • Lists built with the wrong markup WCAG 1.3.1 · 2 places
Overlay widget
UserWay
No detectable failures

Orange County

Home page tested: orangecountyfl.net

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
Recite Me
1 check failed

Osceola County

Home page tested: osceola.org · 9 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 9 places
Overlay widget
None found
Accessibility link
None found on the home page
2 checks failed

Palm Beach County

Home page tested: discover.pbc.gov · 7 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 4 places
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 3 places
Overlay widget
None found
1 check failed

Pasco County

Home page tested: pascocountyfl.gov · 3 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 3 places
Overlay widget
None found
No detectable failures

Pinellas County

Home page tested: pinellas.gov

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
Accessibility link
Yes, to pinellas.gov/accessibility
1 check failed

Polk County

Home page tested: polkfl.gov · 10 failures in total

  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 10 places
Overlay widget
None found
Accessibility link
Yes, to polkfl.gov/accessibility
1 check failed

Putnam County

Home page tested: putnam-fl.gov · 3 failures in total

  • Controls nested inside other controls WCAG 4.1.2 · 3 places
Overlay widget
UserWay
Accessibility link
Yes, to putnam-fl.gov/accessibility-statement
2 checks failed

Santa Rosa County

Home page tested: santarosa.fl.gov · 3 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
  • Lists built with the wrong markup WCAG 1.3.1 · 1 place
Overlay widget
AudioEye
Accessibility link
Yes, to santarosa.fl.gov/accessibility
No detectable failures

Sarasota County

Home page tested: scgov.net

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
1 check failed

Seminole County

Home page tested: seminolecountyfl.gov · 2 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
Overlay widget
UserWay
No detectable failures

St. Johns County

Home page tested: sjcfl.us

The automated test found no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof of conformance.

Overlay widget
None found
1 check failed

St. Lucie County

Home page tested: stlucieco.gov · 3 failures in total

  • Lists built with the wrong markup WCAG 1.3.1 · 3 places
Overlay widget
None found
2 checks failed

Sumter County

Home page tested: sumtercountyfl.gov · 3 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 2 places
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
None found
Accessibility link
Yes, to sumtercountyfl.gov/Accessibility
3 checks failed

Suwannee County

Home page tested: suwanneecountyfl.gov · 4 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
  • Images with no text alternative WCAG 1.1.1 · 1 place
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 1 place
Overlay widget
AudioEye
Accessibility link
None found on the home page
1 check failed

Taylor County

Home page tested: taylorcountygov.com · 1 failure in total

  • Scrolling marquee text WCAG 2.2.2 · 1 place
Overlay widget
UserWay
Accessibility link
None found on the home page
2 checks failed

Union County

Home page tested: unioncounty-fl.gov · 3 failures in total

  • Text with too little contrast against its background WCAG 1.4.3 · 2 places
  • Links that only color sets apart from the text around them WCAG 1.4.1 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
3 checks failed

Volusia County

Home page tested: volusia.org · 5 failures in total

  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 3 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 1 place
  • Text with too little contrast against its background WCAG 1.4.3 · 1 place
Overlay widget
None found
Accessibility link
None found on the home page
4 checks failed

Wakulla County

Home page tested: mywakulla.com · 1,284 failures in total

  • Hidden content that keyboard focus can still land on WCAG 4.1.2 · 1,267 places
  • Text with too little contrast against its background WCAG 1.4.3 · 11 places
  • Buttons with no name a screen reader can announce WCAG 4.1.2 · 4 places
  • ARIA attributes used where they are not allowed WCAG 4.1.2 · 2 places
Overlay widget
UserWay
2 checks failed

Walton County

Home page tested: mywaltonfl.gov · 10 failures in total

  • Images with no text alternative WCAG 1.1.1 · 5 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 5 places
Overlay widget
Accessibility Enabled / Monsido
Accessibility link
Yes, to mywaltonfl.gov/accessibility
5 checks failed

Washington County

Home page tested: washingtonfl.gov · 38 failures in total

  • Images with no text alternative WCAG 1.1.1 · 21 places
  • Text with too little contrast against its background WCAG 1.4.3 · 8 places
  • Links with no name a screen reader can announce WCAG 2.4.4, 4.1.2 · 5 places
  • Lists built with the wrong markup WCAG 1.3.1 · 3 places
  • Links that only color sets apart from the text around them WCAG 1.4.1 · 1 place
Overlay widget
None found

Let's talk about your project!

Send a short note about what needs to change. We’ll reply personally, talk through scope and budget, and arrange a conversation if it would help.

Tell us about your project

Prefer email? hello@awesomecause.com

Tell us about your project

Start with a short note.

Tell us a little about the project. We’ll reply personally within one business day and arrange a time to talk if it would help.

What do you need?
Two or three sentences is plenty.

Prefer email? hello@awesomecause.com. No newsletters, no spam, ever.