Skip to main content
throughline
Trust & accuracy

Built so it can't guess.

When a benefit, a renewal or your child's eligibility is on the line, a confident wrong answer is worse than no answer. So Throughline drops any number it can't trace to your letter.

Traced to the Page

Throughline takes only what is printed on your document, and every value carries a pointer to the line it came from. One check runs on all of them. A value that can't be traced to the page is dropped, and in its place you see a note to confirm it with the office that sent the letter. An automated test tries to make the engine invent a number and confirms it can't.

We explain, we never advise

Throughline is not a law firm, a benefits-planning service, or a financial advisor. It will not tell you what to do, decide who qualifies, or draft a legal document. Only the Social Security Administration, your state Medicaid office, or the school district can decide eligibility. We explain what your documents say and route you to the exact office that handles it. We name the door. We never claim the key.

A sourced rules library

The deadlines and amounts we show come from a library of 62 rules, each keyed to a jurisdiction and year and carrying its source and an “as of” date. SSI limits, Medicaid income thresholds and filing windows change every year and vary by state, so every one is flagged for you to confirm with the office named on it.

This library is a starting point under review. Treat every date and amount as a prompt to check with the office, above all for state Medicaid and waiver rules.

Accessible and calm, on purpose.

The people reading this are tired caregivers, and self-advocates who may use a screen reader, a keyboard or extra time. So accessibility is a requirement here, and we hold ourselves to WCAG 2.2 AA.

  • 1.4.3 · AA

    Contrast (minimum)

    Body text meets at least 4.5:1 and large text 3:1 against its background. The token palette is chosen and documented to pass.

  • 1.4.11 · AA

    Non-text contrast

    Interactive controls, focus rings, and meaningful borders meet 3:1 against adjacent colors.

  • 2.1.1 · A

    Keyboard

    Every interactive element is reachable and operable by keyboard alone; no keyboard traps.

  • 2.4.1 · A

    Bypass blocks

    A skip link jumps past navigation to the main content.

  • 2.4.7 · AA

    Focus visible

    A single, high-contrast focus ring is applied consistently via the shared FOCUS_RING utility.

  • 2.4.11 · AA

    Focus not obscured (minimum)

    Sticky headers leave scroll padding so a focused element is never hidden behind them.

  • 2.5.8 · AA

    Target size (minimum)

    Interactive targets are at least 24×24 CSS px; primary actions are 44px tall for comfort.

  • 3.1.5 · AAA

    Reading level

    Explanations are written at roughly an 8th-grade reading level; no jargon without a plain gloss.

  • 3.3.1 · A

    Error identification

    Form errors are announced in text and associated to their field via aria-describedby + aria-invalid.

  • 3.3.2 · A

    Labels or instructions

    Every input has a visible, programmatically-associated label and optional help text.

  • 4.1.2 · A

    Name, role, value

    Components forward native semantics (button, links, inputs) and ARIA only where native semantics fall short.

  • 2.3.3 · AAA

    Animation from interactions

    All non-essential motion is disabled under prefers-reduced-motion.