SupportDecode

Accessibility statement

Last reviewed:

The people who use this site are often stressed, on a phone, late at night. Accessibility is not an extra here; it is part of the product. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the whole site.

What is implemented today

  • Every calculator can be completed with a keyboard alone, and a skip link jumps past the navigation to the main content.
  • Focus is always visible, with a consistent focus ring on interactive elements.
  • Every form field has a visible label, and validation problems are announced in an error summary that links to the field.
  • Calculator results update through live regions, so screen readers announce new results without a page reload.
  • Text and interface colors meet AA contrast ratios, and meaning is never carried by color alone; the state map pairs its colors with a text legend and a full table alternative.
  • Animations are removed for visitors whose system asks for reduced motion.
  • Results print cleanly: print styles strip navigation and keep the numbers, dates, and disclaimers.
  • Touch targets are at least 44 by 44 pixels.
  • Content pages work without JavaScript. Where a tool needs it, such as the interactive map, a plain table fallback renders when JavaScript is off.

Known limitations

Honesty over polish. These are the weak spots we know about:

  • The interactive US map is a complex SVG. Small northeastern states get separate callout targets, but precise pointer work on a small phone can still be fiddly. The state table below the map always carries the same information.
  • Some testing at the narrowest phone widths was done with browser emulation rather than on physical devices, so a layout issue on a specific device may have slipped past us.
  • We link to official statutes, guideline PDFs, and state calculators. Those documents live on government sites and some, especially older PDFs, are not accessible; we cannot fix them, but we summarize the key numbers in accessible HTML on our pages.

Tell us what is broken

If anything on this site is hard to use with a screen reader, a keyboard, a switch device, or magnification, please report it through the contact page. Accessibility reports get the same treatment as factual corrections: we triage them within 48 hours, and fixes are listed on the updates page.