Jefferson County (AL) — Score 977 | Sonde

Sonde

Accessibility Health Check

https://jeffersoncountyal.gov

Excellent

April 28, 2026

Provided free by Sonde

1pages8findings0critical5high3medium0low8.0avg/page35elements6with findings82.9%ECR26.3stotal26.3sper page

Excellent

Executive Summary

1pages8findings8.0avg/page35elements6with findings82.9%ECR26.3stotal26.3sper page

Top Findings

Copy a direct link to share a finding Open a discussion to give feedback on a finding

highImage has no accessible name in the accessibility tree. Screen readers will skip or announce it generically.WCAG 1.1.1
Element:
<!-- a11y: role="image" -->
Sonde Fix Plan

Add alt text to the image. If decorative, mark with role="presentation" or alt="". WCAG 1.1.1 requires text alternatives for non-text content.

highInsufficient color contrast: 2.38:1 (required: 4.5:1 for normal text). Foreground: rgb(143, 143, 143), background: rgb(221, 221, 221). Text: "Check if there is a typo in jeffersoncountyal.gov."WCAG 1.4.3
Element:
<div id="sub-frame-error-details">Check if there is a typo in <span>jeffersoncountyal.gov</span>.</div>
Sonde Fix Plan

Current ratio: 2.38:1 (need 4.5:1). Change foreground from #8f8f8f to #626161 (ratio: 4.5:1).

highInsufficient color contrast: 2.38:1 (required: 4.5:1 for normal text). Foreground: rgb(143, 143, 143), background: rgb(221, 221, 221). Text: "jeffersoncountyal.gov"WCAG 1.4.3
Element:
<span>jeffersoncountyal.gov</span>
Sonde Fix Plan

Current ratio: 2.38:1 (need 4.5:1). Change foreground from #8f8f8f to #626161 (ratio: 4.5:1).

highPage has no detectable navigation mechanisms (no <nav>, search, sitemap link, breadcrumbs, or table of contents). Users need multiple ways to locate content.WCAG 2.4.5
Sonde Fix Plan

Add at least two of: site navigation (<nav>), search functionality (input[type="search"] or role="search"), a sitemap link, breadcrumb navigation, or a table of contents.

highMissing Strict-Transport-Security header (HSTS)
Page: /
Sonde Fix Plan

Add Strict-Transport-Security header with max-age of at least 31536000 Add X-Content-Type-Options: nosniff Add X-Frame-Options: DENY or SAMEORIGIN Add a Content-Security-Policy header with appropriate directives Add Referrer-Policy: strict-origin-when-cross-origin or no-referrer

mediumAll page content should be contained by landmarks: Fix any of the following: Some page content is not contained by landmarks
Page: /
Element:
<div id="main-content">
Sonde Fix Plan

Ensure all page content is contained by landmarks. See: https://www.w3.org/WAI/WCAG22/quickref/

mediumZooming and scaling must not be disabled: Fix any of the following: user-scalable=no on <meta> tag disables zooming on mobile devicesWCAG 1.4.4
Element:
<meta name="viewport" content="width=device-width, initial-scale=1.0,
                                 maximum-scale=1.0, user-scalable=no">
Sonde Fix Plan

Ensure <meta name="viewport"> does not disable text scaling and zooming. See: https://www.w3.org/WAI/WCAG22/Understanding/resize-text

mediumDocument should have one main landmark: Fix all of the following: Document does not have a main landmark
Page: /
Element:
<html dir="ltr" lang="en">
Sonde Fix Plan

Ensure the document has a main landmark. See: https://www.w3.org/WAI/WCAG22/quickref/

Best Page Fix Opportunities

chromewebdata8findings
highImage has no accessible name in the accessibility tree. Screen readers will skip or announce it generically.WCAG 1.1.1
Element:
<!-- a11y: role="image" -->
Sonde Fix Plan

Add alt text to the image. If decorative, mark with role="presentation" or alt="". WCAG 1.1.1 requires text alternatives for non-text content.

highInsufficient color contrast: 2.38:1 (required: 4.5:1 for normal text). Foreground: rgb(143, 143, 143), background: rgb(221, 221, 221). Text: "Check if there is a typo in jeffersoncountyal.gov."WCAG 1.4.3
Element:
<div id="sub-frame-error-details">Check if there is a typo in <span>jeffersoncountyal.gov</span>.</div>
Sonde Fix Plan

Current ratio: 2.38:1 (need 4.5:1). Change foreground from #8f8f8f to #626161 (ratio: 4.5:1).

highInsufficient color contrast: 2.38:1 (required: 4.5:1 for normal text). Foreground: rgb(143, 143, 143), background: rgb(221, 221, 221). Text: "jeffersoncountyal.gov"WCAG 1.4.3
Element:
<span>jeffersoncountyal.gov</span>
Sonde Fix Plan

Current ratio: 2.38:1 (need 4.5:1). Change foreground from #8f8f8f to #626161 (ratio: 4.5:1).

highPage has no detectable navigation mechanisms (no <nav>, search, sitemap link, breadcrumbs, or table of contents). Users need multiple ways to locate content.WCAG 2.4.5
Sonde Fix Plan

Add at least two of: site navigation (<nav>), search functionality (input[type="search"] or role="search"), a sitemap link, breadcrumb navigation, or a table of contents.

highMissing Strict-Transport-Security header (HSTS)
Page: /
Sonde Fix Plan

Add Strict-Transport-Security header with max-age of at least 31536000 Add X-Content-Type-Options: nosniff Add X-Frame-Options: DENY or SAMEORIGIN Add a Content-Security-Policy header with appropriate directives Add Referrer-Policy: strict-origin-when-cross-origin or no-referrer

mediumAll page content should be contained by landmarks: Fix any of the following: Some page content is not contained by landmarks
Page: /
Element:
<div id="main-content">
Sonde Fix Plan

Ensure all page content is contained by landmarks. See: https://www.w3.org/WAI/WCAG22/quickref/

mediumZooming and scaling must not be disabled: Fix any of the following: user-scalable=no on <meta> tag disables zooming on mobile devicesWCAG 1.4.4
Element:
<meta name="viewport" content="width=device-width, initial-scale=1.0,
                                 maximum-scale=1.0, user-scalable=no">
Sonde Fix Plan

Ensure <meta name="viewport"> does not disable text scaling and zooming. See: https://www.w3.org/WAI/WCAG22/Understanding/resize-text

mediumDocument should have one main landmark: Fix all of the following: Document does not have a main landmark
Page: /
Element:
<html dir="ltr" lang="en">
Sonde Fix Plan

Ensure the document has a main landmark. See: https://www.w3.org/WAI/WCAG22/quickref/

Methodology

The Sonde Score is a universal 0–1000 compliance index — think of it like a credit score for accessibility. Each finding is weighted by its impact on human access: a keyboard trap (critical) counts far more than a best-practice suggestion (low). The raw penalty is normalized per page so scores are comparable across sites of any size. A harmonic curve ensures every site gets a meaningful score — no zeros, no false perfection.

Score = round(1000 × S / (S + P/N))

where S = sensitivity (750), P = Σ(weight × count), N = pages scanned

TierWeightExamples
Critical10Keyboard traps, missing page language
High3Missing alt text, insufficient contrast
Medium1Heading hierarchy, unclear link purpose
Low0.25Best-practice suggestions

The Sonde Score is a living standard (v0.1). We’re building it in the open because accessibility is too important for closed-door decisions. Your expertise makes it better.

Enter Mission Control

Review raw findings data, track changes between scans, and contribute to Sonde’s open methodology.

Nominate a Site for the Daylight Index

Know a public website that should be on the accessibility leaderboard? Nominate it — we’ll scan it and publish the results.

Nominate a Site →

This report is a health check, not a verdict. Every website has room to improve.

Disclaimer: This report presents the results of automated accessibility analysis and is provided free of charge, as-is, without warranty of any kind. Findings are generated by software, not by human accessibility experts, and may contain errors or omissions. Automated testing can detect approximately 30–40% of accessibility issues; manual expert evaluation is recommended for complete conformance assessment. Scores reflect algorithmic analysis under a published methodology open to public review — they are not legal determinations of compliance. Results reflect the state of the website at the time of scanning and may change as the site is updated. Nothing in this report constitutes legal advice. Sonde assumes no liability for decisions made based on these results.

Compliance methodology: NIST 800-53 Rev 5 (usnistgov/oscal-content v1.4.0, catalog 5.2.0) · NIST PRIVACY overlay (usnistgov/oscal-content v1.4.0, catalog 5.2.0) · FedRAMP Rev 5 (OSCAL-Foundation/fedramp-resources a6b85ed451, catalog fedramp-3.0.0rc1-oscal-1.1.2).