Accessibility

Our Target

CountyPulse aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Accessibility is treated as a load-bearing requirement, not a finishing touch. Reports of accessibility issues are prioritized alongside data bugs.

What's Supported

• Keyboard navigation. Every interactive element is reachable by Tab with a visible focus outline. A “Skip to main content” link is available on every page.
• Semantic HTML. Headings, lists, tables, and landmarks use their native elements so screen readers can navigate them correctly.
• Color contrast. Body text, labels, and interactive states meet the 4.5:1 contrast ratio required by WCAG AA. The design uses color alongside — not instead of — text labels.
• No motion-required interactions. Nothing on the site requires animation, auto-play, gestures, or precise pointer control to use.
• Scalable text. Text resizes with the browser's zoom and font-size settings without clipping or overflow at 200% zoom.
• Static pages. The site is pre-rendered HTML with minimal JavaScript; assistive technology does not depend on client-side frameworks to read content.

Known Limitations

• Some data tables on county pages are wide; on narrow viewports they scroll horizontally. A keyboard user can still reach every cell with arrow keys.
• Federal agency sites linked from CountyPulse are outside our control, and their accessibility varies.

Report an Issue

If you encounter a page or element that is difficult to use with assistive technology — or fails a specific WCAG criterion — please tell us. Email [email protected] with the URL, what you were trying to do, and the assistive technology you were using. We aim to respond within five business days.