← Read the original reportResearch

50 of 64 Florida county home pages had a detectable accessibility failure

On October 14, 2026 we ran an automated WCAG 2.1 AA test on the home page of each Florida county government website. 14 showed no automated failures. We could not test 3 of the 67 because their sites turned our browser away.

Compare every county Read the original report

78%

of home pages (50 of 64) failed at least one check

1.5

failed checks on the median home page; the most on any one page was 7

home pages had no automated failures detected, which is not proof they work for everyone

load an accessibility overlay; 27 of them still failed a check

What the failures look like

Most home pages failed a few checks, not dozens. Every bar below is also a row with its numbers written out.

How many checks each page failed

Home pages by number of failed checks (64 scanned)
Failed checks	Counties	Bar
None detected	14 of 64 (22%)
1 failed check	18 of 64 (28%)
2 failed checks	12 of 64 (19%)
3 failed checks	7 of 64 (11%)
4 failed checks	8 of 64 (13%)
5 failed checks	2 of 64 (3%)
6 failed checks	2 of 64 (3%)
7 failed checks	1 of 64 (2%)

Overlays and failures

Home pages with at least one failed check, by whether they load an overlay
Home pages that…	Counties	Bar
load an accessibility overlay	27 of 31 (87%)
load no overlay	23 of 33 (70%)

An overlay is a widget added on top of a page. It doesn’t change the page’s own code, which is what these checks test.

What failed most often

The 8 checks failed by the most counties
What failed	Counties	Bar
Text with too little contrast against its backgroundWCAG 1.4.3	25 of 64 (39%)
Links with no name a screen reader can announceWCAG 2.4.4, 4.1.2	23 of 64 (36%)
ARIA attributes used where they are not allowedWCAG 4.1.2	10 of 64 (16%)
Buttons with no name a screen reader can announceWCAG 4.1.2	10 of 64 (16%)
Lists built with the wrong markupWCAG 1.3.1	9 of 64 (14%)
Images with no text alternativeWCAG 1.1.1	8 of 64 (13%)
ARIA attributes the element’s role doesn’t supportWCAG 4.1.2	6 of 64 (9%)
Hidden content that keyboard focus can still land onWCAG 4.1.2	5 of 64 (8%)

Each check is counted separately, so related ARIA checks are not combined here. 14 other checks were failed by fewer counties.

Every county, side by side

Sort by any column. Each county name links to its full findings further down the page.

How the score works

Score = 100 − 10 × the number of failed checks, never below 0. A page that failed 3 checks scores 70. The lowest score in this data is 30. A 100 means no automated failures detected; it does not mean the page works for everyone. We count checks, not places, because one broken template can fail in hundreds of places and still be one fix. The Places column shows that count too.

100 No automated failures detected
80–90 1 to 2 failed checks
60–70 3 to 4 failed checks
30–50 5 or more failed checks

Home page results for all 67 counties. Select a column heading to sort.
County	Score	Failed checks	Places	Overlay	Accessibility link
Alachua	90	1	1	No	Yes
Baker	Not tested (site blocked our browser)
Bay	100	None	0	Yes	No
Bradford	80	2	3	Yes	No
Brevard	100	None	0	No	Yes
Broward	60	4	30	Yes	Yes
Calhoun	Not tested (site blocked our browser)
Charlotte	60	4	20	Yes	No
Citrus	40	6	23	Yes	Yes
Clay	80	2	9	Yes	Yes
Collier	100	None	0	No	Yes
Columbia	100	None	0	No	No
DeSoto	90	1	1	Yes	Yes
Dixie	60	4	22	Yes	Yes
Duval	100	None	0	No	Yes
Escambia	90	1	2	Yes	Yes
Flagler	100	None	0	Yes	Yes
Franklin	100	None	0	No	Yes
Gadsden	80	2	6	No	No
Gilchrist	30	7	7	Yes	Yes
Glades	70	3	7	Yes	Yes
Gulf	80	2	3	No	No
Hamilton	90	1	2	Yes	No
Hardee	Not tested (site blocked our browser)
Hendry	70	3	160	No	Yes
Hernando	90	1	2	Yes	Yes
Highlands	70	3	27	Yes	Yes
Hillsborough	90	1	18	Yes	Yes
Holmes	90	1	2	Yes	Yes
Indian River	100	None	0	Yes	No
Jackson	60	4	9	No	Yes
Jefferson	90	1	1	No	Yes
Lafayette	90	1	1	No	Yes
Lake	90	1	1	Yes	Yes
Lee	70	3	4	No	No
Leon	100	None	0	No	Yes
Levy	90	1	2	Yes	Yes
Liberty	80	2	2	Yes	Yes
Madison	50	5	7	No	Yes
Manatee	80	2	2	No	Yes
Marion	60	4	19	Yes	Yes
Martin	100	None	0	No	Yes
Miami-Dade	60	4	10	No	No
Monroe	60	4	13	No	Yes
Nassau	70	3	3	No	Yes
Okaloosa	40	6	34	No	Yes
Okeechobee	80	2	4	Yes	Yes
Orange	100	None	0	Yes	Yes
Osceola	90	1	9	No	No
Palm Beach	80	2	7	No	Yes
Pasco	90	1	3	No	Yes
Pinellas	100	None	0	No	Yes
Polk	90	1	10	No	Yes
Putnam	90	1	3	Yes	Yes
Santa Rosa	80	2	3	Yes	Yes
Sarasota	100	None	0	No	Yes
Seminole	90	1	2	Yes	Yes
St. Johns	100	None	0	No	Yes
St. Lucie	90	1	3	No	Yes
Sumter	80	2	3	No	Yes
Suwannee	70	3	4	Yes	No
Taylor	90	1	1	Yes	No
Union	80	2	3	No	No
Volusia	70	3	5	No	No
Wakulla	60	4	1,284	Yes	Yes
Walton	80	2	10	Yes	Yes
Washington	50	5	38	No	Yes

The overlay and accessibility link columns show on wider screens. Every county’s findings below include them.

Findings for each county

The checks each home page failed, how many places, the overlay it loads and whether it links to an accessibility page.

1 check failed

Alachua County

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

Score 90 out of 100

Definition lists built with the wrong markup WCAG 1.3.1 · 1 place

Overlay widget: None found
Accessibility link: Yes, to alachuacounty.us/Depts/EO/Pages/Website-Accessibility.aspx

Work for Alachua County? Check alachuacounty.us today with Awesome Audit, free.

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.

Work for Baker County? Check bakercountyfl.org today with Awesome Audit, free.

No automated failures detected

Bay County

Home page tested: baycountyfl.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: UserWay
Accessibility link: None found on the home page

Work for Bay County? Check baycountyfl.gov today with Awesome Audit, free.

2 checks failed

Bradford County

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

Score 80 out of 100

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

Work for Bradford County? Check bradfordcountyfl.gov today with Awesome Audit, free.

No automated failures detected

Brevard County

Home page tested: brevardfl.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to brevardfl.gov/Accessibility

Work for Brevard County? Check brevardfl.gov today with Awesome Audit, free.

4 checks failed

Broward County

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

Score 60 out of 100

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

Work for Broward County? Check broward.org today with Awesome Audit, free.

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.

Work for Calhoun County? Check calhouncountyfl.org today with Awesome Audit, free.

4 checks failed

Charlotte County

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

Score 60 out of 100

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

Work for Charlotte County? Check charlottecountyfl.gov today with Awesome Audit, free.

6 checks failed

Citrus County

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

Score 40 out of 100

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
Accessibility link: Yes, to citruscounty.gov/accessibility_statement/index.php

Work for Citrus County? Check citruscounty.gov today with Awesome Audit, free.

2 checks failed

Clay County

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

Score 80 out of 100

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
Accessibility link: Yes, to claycountygov.com/government/accessibility

Work for Clay County? Check claycountygov.com today with Awesome Audit, free.

No automated failures detected

Collier County

Home page tested: collier.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to collier.gov/Collier-County/Communications-Government-Public-Affairs/Accessibility

Work for Collier County? Check collier.gov today with Awesome Audit, free.

No automated failures detected

Columbia County

Home page tested: columbiacountyfla.com

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: None found on the home page

Work for Columbia County? Check columbiacountyfla.com today with Awesome Audit, free.

1 check failed

DeSoto County

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

Score 90 out of 100

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

Work for DeSoto County? Check desotobocc.com today with Awesome Audit, free.

4 checks failed

Dixie County

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

Score 60 out of 100

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
Accessibility link: Yes, to accessibe.com/blog/knowledgebase/screen-reader-guide

Work for Dixie County? Check dixiecounty.us today with Awesome Audit, free.

No automated failures detected

Duval County (Consolidated with the City of Jacksonville)

Home page tested: jacksonville.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to jacksonville.gov/accessibility

Work for Duval County? Check jacksonville.gov today with Awesome Audit, free.

1 check failed

Escambia County

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

Score 90 out of 100

ARIA attributes used where they are not allowed WCAG 4.1.2 · 2 places

Overlay widget: UserWay
Accessibility link: Yes, to myescambia.com/open-government/americans-with-disabilities-act/accessibility

Work for Escambia County? Check myescambia.com today with Awesome Audit, free.

No automated failures detected

Flagler County

Home page tested: flaglercounty.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: accessiBe
Accessibility link: Yes, to accessibe.com/blog/knowledgebase/screen-reader-guide

Work for Flagler County? Check flaglercounty.gov today with Awesome Audit, free.

No automated failures detected

Franklin County

Home page tested: franklincountyflorida.com

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to franklincountyflorida.com/accessibility-policy

Work for Franklin County? Check franklincountyflorida.com today with Awesome Audit, free.

2 checks failed

Gadsden County

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

Score 80 out of 100

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

Work for Gadsden County? Check gadsdencountyfl.gov today with Awesome Audit, free.

7 checks failed

Gilchrist County

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

Score 30 out of 100

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

Work for Gilchrist County? Check gilchrist.fl.us today with Awesome Audit, free.

3 checks failed

Glades County

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

Score 70 out of 100

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
Accessibility link: Yes, to myglades.com/accessibility_use/index.php

Work for Glades County? Check myglades.com today with Awesome Audit, free.

2 checks failed

Gulf County

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

Score 80 out of 100

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

Work for Gulf County? Check gulfcounty-fl.gov today with Awesome Audit, free.

1 check failed

Hamilton County

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

Score 90 out of 100

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

Work for Hamilton County? Check hamiltoncountyfl.com today with Awesome Audit, free.

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.

Work for Hardee County? Check hardeecountyfl.gov today with Awesome Audit, free.

3 checks failed

Hendry County

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

Score 70 out of 100

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
Accessibility link: Yes, to hendryfla.net/accessibility_statement/statement.php

Work for Hendry County? Check hendryfla.net today with Awesome Audit, free.

1 check failed

Hernando County

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

Score 90 out of 100

Graphics marked as images with no text alternative WCAG 1.1.1 · 2 places

Overlay widget: UserWay
Accessibility link: Yes, to hernandocounty.us/county-government/accessibility

Work for Hernando County? Check hernandocounty.us today with Awesome Audit, free.

3 checks failed

Highlands County

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

Score 70 out of 100

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
Accessibility link: Yes, to hcbcc.net/accessibility_statement/index.php

Work for Highlands County? Check hcbcc.net today with Awesome Audit, free.

1 check failed

Hillsborough County

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

Score 90 out of 100

Text with too little contrast against its background WCAG 1.4.3 · 18 places

Overlay widget: UserWay
Accessibility link: Yes, to hcfl.gov/residents/human-services/special-needs/ada-guide-to-services

Work for Hillsborough County? Check hcfl.gov today with Awesome Audit, free.

1 check failed

Holmes County

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

Score 90 out of 100

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

Work for Holmes County? Check holmescountyfla.com today with Awesome Audit, free.

No automated failures detected

Indian River County

Home page tested: indianriver.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: UserWay
Accessibility link: None found on the home page

Work for Indian River County? Check indianriver.gov today with Awesome Audit, free.

4 checks failed

Jackson County

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

Score 60 out of 100

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
Accessibility link: Yes, to jacksoncountyfl.gov/accessibility-policy

Work for Jackson County? Check jacksoncountyfl.gov today with Awesome Audit, free.

1 check failed

Jefferson County

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

Score 90 out of 100

Text with too little contrast against its background WCAG 1.4.3 · 1 place

Overlay widget: None found
Accessibility link: Yes, to jeffersoncountyfl.gov/accessibility-statement

Work for Jefferson County? Check jeffersoncountyfl.gov today with Awesome Audit, free.

1 check failed

Lafayette County

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

Score 90 out of 100

ARIA buttons, links or menu items with no name WCAG 4.1.2 · 1 place

Overlay widget: None found
Accessibility link: Yes, to lafayettecountyfl.org/accessibility-policy

Work for Lafayette County? Check lafayettecountyfl.org today with Awesome Audit, free.

1 check failed

Lake County

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

Score 90 out of 100

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

Work for Lake County? Check lakecountyfl.gov today with Awesome Audit, free.

3 checks failed

Lee County

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

Score 70 out of 100

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

Work for Lee County? Check leegov.com today with Awesome Audit, free.

No automated failures detected

Leon County

Home page tested: cms.leoncountyfl.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to cms.leoncountyfl.gov/Accessibility

Work for Leon County? Check cms.leoncountyfl.gov today with Awesome Audit, free.

1 check failed

Levy County

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

Score 90 out of 100

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

Work for Levy County? Check levycounty.org today with Awesome Audit, free.

2 checks failed

Liberty County

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

Score 80 out of 100

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
Accessibility link: Yes, to libertycountyfl.org/accessibility-policy

Work for Liberty County? Check libertycountyfl.org today with Awesome Audit, free.

5 checks failed

Madison County

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

Score 50 out of 100

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
Accessibility link: Yes, to madisoncountyfl.com/accessibility-policy

Work for Madison County? Check madisoncountyfl.com today with Awesome Audit, free.

2 checks failed

Manatee County

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

Score 80 out of 100

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: Yes, to mymanatee.org/services-and-amenities/infrastructure--safety-and-environment/accessibility-and-mobility

Work for Manatee County? Check mymanatee.org today with Awesome Audit, free.

4 checks failed

Marion County

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

Score 60 out of 100

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

Work for Marion County? Check marionfl.org today with Awesome Audit, free.

No automated failures detected

Martin County

Home page tested: martin.fl.us

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

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

Work for Martin County? Check martin.fl.us today with Awesome Audit, free.

4 checks failed

Miami-Dade County

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

Score 60 out of 100

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

Work for Miami-Dade County? Check miamidade.gov today with Awesome Audit, free.

4 checks failed

Monroe County

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

Score 60 out of 100

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

Work for Monroe County? Check monroecounty-fl.gov today with Awesome Audit, free.

3 checks failed

Nassau County

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

Score 70 out of 100

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

Work for Nassau County? Check nassaucountyfl.com today with Awesome Audit, free.

6 checks failed

Okaloosa County

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

Score 40 out of 100

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
Accessibility link: Yes, to skynettechnologies.com/all-in-one-accessibility

Work for Okaloosa County? Check myokaloosa.com today with Awesome Audit, free.

2 checks failed

Okeechobee County

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

Score 80 out of 100

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
Accessibility link: Yes, to okeechobeecountyfl.gov/departments/site-specific-pages/accessibility

Work for Okeechobee County? Check okeechobeecountyfl.gov today with Awesome Audit, free.

No automated failures detected

Orange County

Home page tested: orangecountyfl.net

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: Recite Me
Accessibility link: Yes, to orangecountyfl.net/AccessibilityHelp.aspx

Work for Orange County? Check orangecountyfl.net today with Awesome Audit, free.

1 check failed

Osceola County

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

Score 90 out of 100

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

Work for Osceola County? Check osceola.org today with Awesome Audit, free.

2 checks failed

Palm Beach County

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

Score 80 out of 100

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
Accessibility link: Yes, to discover.pbc.gov/Pages/Accessibility-Statement-Resources.aspx

Work for Palm Beach County? Check discover.pbc.gov today with Awesome Audit, free.

1 check failed

Pasco County

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

Score 90 out of 100

Text with too little contrast against its background WCAG 1.4.3 · 3 places

Overlay widget: None found
Accessibility link: Yes, to pascocountyfl.gov/how_do_i/view/accessibility.php

Work for Pasco County? Check pascocountyfl.gov today with Awesome Audit, free.

No automated failures detected

Pinellas County

Home page tested: pinellas.gov

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

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

Score 90 out of 100

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

Work for Polk County? Check polkfl.gov today with Awesome Audit, free.

1 check failed

Putnam County

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

Score 90 out of 100

Controls nested inside other controls WCAG 4.1.2 · 3 places

Overlay widget: UserWay
Accessibility link: Yes, to putnam-fl.gov/accessibility-statement

Work for Putnam County? Check putnam-fl.gov today with Awesome Audit, free.

2 checks failed

Santa Rosa County

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

Score 80 out of 100

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

Work for Santa Rosa County? Check santarosa.fl.gov today with Awesome Audit, free.

No automated failures detected

Sarasota County

Home page tested: scgov.net

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to scgov.net/government/county-administration/ethics-and-compliance/ada-title-vi-compliance/website-accessibility

Work for Sarasota County? Check scgov.net today with Awesome Audit, free.

1 check failed

Seminole County

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

Score 90 out of 100

Text with too little contrast against its background WCAG 1.4.3 · 2 places

Overlay widget: UserWay
Accessibility link: Yes, to seminolecountyfl.gov/departments-services/guide-to-county-services/about-seminole-county/accessibility-policy

Work for Seminole County? Check seminolecountyfl.gov today with Awesome Audit, free.

No automated failures detected

St. Johns County

Home page tested: sjcfl.us

Score 100 out of 100

The automated test detected no WCAG 2.1 A or AA failures on the home page. That is a good sign, not proof that the site works for everyone.

Overlay widget: None found
Accessibility link: Yes, to sjcfl.us/your-government-2/civil-rights-act-americans-with-disabilities-act

Work for St. Johns County? Check sjcfl.us today with Awesome Audit, free.

1 check failed

St. Lucie County

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

Score 90 out of 100

Lists built with the wrong markup WCAG 1.3.1 · 3 places

Overlay widget: None found
Accessibility link: Yes, to stlucieco.gov/government/accessibility-statement

Work for St. Lucie County? Check stlucieco.gov today with Awesome Audit, free.

2 checks failed

Sumter County

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

Score 80 out of 100

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

Work for Sumter County? Check sumtercountyfl.gov today with Awesome Audit, free.

3 checks failed

Suwannee County

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

Score 70 out of 100

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

Work for Suwannee County? Check suwanneecountyfl.gov today with Awesome Audit, free.

1 check failed

Taylor County

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

Score 90 out of 100

Scrolling marquee text WCAG 2.2.2 · 1 place

Overlay widget: UserWay
Accessibility link: None found on the home page

Work for Taylor County? Check taylorcountygov.com today with Awesome Audit, free.

2 checks failed

Union County

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

Score 80 out of 100

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

Work for Union County? Check unioncounty-fl.gov today with Awesome Audit, free.

3 checks failed

Volusia County

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

Score 70 out of 100

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

Work for Volusia County? Check volusia.org today with Awesome Audit, free.

4 checks failed

Wakulla County

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

Score 60 out of 100

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
Accessibility link: Yes, to mywakulla.com/residents/ada_website_accessibility.php

Work for Wakulla County? Check mywakulla.com today with Awesome Audit, free.

2 checks failed

Walton County

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

Score 80 out of 100

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

Work for Walton County? Check mywaltonfl.gov today with Awesome Audit, free.

5 checks failed

Washington County

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

Score 50 out of 100

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
Accessibility link: Yes, to washingtonfl.gov/departments/administration/accessibility

Work for Washington County? Check washingtonfl.gov today with Awesome Audit, free.

Method and limits

What we tested: one page, the home page, in a desktop browser 1,280 pixels wide on October 14, 2026, with axe-core 4.13 set to the WCAG 2.0 and 2.1 Level A and AA rules.
What a failed check is: axe-core reported at least one violation of that rule. A place is one element on the page that failed. Total places across all 64 home pages: 1,845.
What a clean result means: the software found no failures. Automated tests find only some barriers, so these results are not an audit and a clean result does not show a site works for everyone. 15 of the 64 home pages have no link that mentions accessibility.
Not tested: Baker, Calhoun and Hardee counties, whose sites blocked our automated browser. We did not try to get around the blocks.
Sites change. A page may look different today. If you see a mistake, email hello@awesomecause.com.

The original report explains how we chose the sites, and what these numbers do and don’t say.

Awesome Audit

Check your county’s site today

These results are a snapshot of one page on October 14, 2026. Awesome Audit, our free accessibility check, looks at your home page and up to 25 more pages as they are now. In about 10 minutes you get a letter grade and the biggest problems in plain language, with what to fix first. There is no account to create and no password to share.

Run a free check

Each county above has a link that opens the check with its site filled in. Like any automated test, it finds some problems, not all of them, and it isn’t a compliance certificate.

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