Accessibility

Accessibility Statement

This site aims to meet WCAG 2.2 AA. Here is what that means, what has been done, and how to report something that falls short.

This site strives to meet WCAG 2.2 Level AA — the Web Content Accessibility Guidelines from the W3C. WCAG 2.2 AA is the standard most US public-sector organizations use, and it's the practical baseline for genuinely accessible web design.

Effective date: May 19, 2026

The standard, in plain language.

Meeting WCAG 2.2 AA means the site should be:

  • Perceivable to people who are blind, have low vision, or are colorblind — through proper text alternatives, sufficient color contrast, and content that adapts to user preferences.
  • Operable by keyboard alone (no mouse required) and by assistive technologies like screen readers, switch devices, and voice control.
  • Understandable in language and behavior, with predictable navigation and clear error messages.
  • Robust enough to work across browsers, devices, and assistive technologies, current and future.

What’s been done.

Specific accessibility measures applied across this site:

  • Semantic HTML structure with proper landmarks (header, main, footer, nav).
  • A skip-to-main-content link at the top of every page, visible on focus.
  • A single h1 per page with a logical, unskipped heading hierarchy throughout.
  • All interactive elements reachable by keyboard, with clearly visible focus indicators.
  • Color contrast meets or exceeds WCAG AA ratios — 4.5:1 for body text, 3:1 for large text and non-text elements.
  • Form labels properly associated with inputs; required fields marked both visually and programmatically.
  • ARIA landmarks and labels used where they add value, and avoided where native HTML already provides the semantics.
  • Images use descriptive alternative text; decorative images are marked appropriately so screen readers skip them.
  • Interactive targets meet the WCAG 2.2 minimum size requirement of 24×24 pixels.
  • Disclosure widgets (navigation menus, FAQ accordions, tabbed sections) follow established WAI-ARIA authoring patterns.
  • Reduced motion preferences are respected — animations are suppressed for users who request reduced motion.
  • Content is structured so it remains readable and operable when zoomed to 200% without horizontal scrolling.

Known limitations.

No site is perfectly accessible, and honesty matters more than claims. Known limitations:

  • Some third-party content occasionally embedded in this site (such as video players, when present) may not meet the same standard as content I control directly.
  • New content may occasionally fail review before being corrected — the site is reviewed regularly, but not in real time.
  • This statement reflects accessibility at publication. Practices and tooling continue to evolve.

If you encounter something specific, please report it using the form below or by email.

How this site is tested.

  • Automated audits using axe-core and Lighthouse, run at build time and periodically thereafter.
  • Manual keyboard navigation testing — every interaction completed without a mouse.
  • Manual screen reader testing on VoiceOver (macOS and iOS) and NVDA (Windows).
  • Color contrast verification with WebAIM’s contrast checker and similar tools.
  • Touch and pointer target measurement against WCAG 2.2 size minimums.