Ctrl+V Access

Paste a bureaucratic denial. Get plain English, your rights, a checklist, and a draft appeal, read aloud if you want it.

Comment

Inspiration

Many people, especially those with disabilities, ADHD, autism, dyslexia, low literacy, or English as a second language, hit an "administrative wall." Letters from health services, disability benefit panels, universities and housing authorities are written in dense legal and bureaucratic language. On the four real-style notices I benchmarked, the Flesch–Kincaid reading level runs from grade 13 to 20.

Appeals work. According to DWP PIP Official Statistics to April 2026 (Table 5Aii), 65% of PIP disability benefit decisions that reach a tribunal are overturned in the claimant's favour. Most people never get that far. The notice is hard to read, the deadline is buried, and the rule the decision rests on is never named.

The Ctrl+V Hackathon asks for technology that helps people reach what they need faster, the way Ctrl+V moves information instantly. So I asked: what if that shortcut were the equalizer? Copy the frightening letter, press Ctrl+V, and get something you can act on.

What It Does

Ctrl+V Access turns the clipboard into an assistive bridge, in both directions: paste the letter in, then copy the appeal and form answers back out.

  1. Two ways in
    • Paste anywhere (Ctrl+V / ⌘+V): a global paste listener picks up a notice pasted anywhere on the page.
    • Rights search: 7 statutory entries covering NICE NG17, PIP, Equality Act 2010, HUD Section 8, NHS FP92A, Access to Work and Warm Home Discount.
  2. Five layers of output
    • 1 · Plain English: bottom line, bullets, jargon dictionary.
    • 2 · Rights: governing rules and citations.
    • 3 · Checklist: steps and evidence, with a progress meter.
    • 4 · Appeal draft: formal reconsideration letter, one-click copy.
    • 5 · Smart Form Bridge: portal questions with answers ready to paste back.
  3. Assistive controls: Bionic Focus, Lexend, high contrast, Web Speech read-aloud, 10 languages via Gemini.

How I Built It

  • React 18, TypeScript, Vite, Tailwind; Node.js / Express 5 API.
  • Google Gemini via @google/genai (gemini-3.5-flash-lite default) with local Flesch–Kincaid fallback.
  • Benchmarks in video/evidence/benchmark.txt: notices 60–74% shorter; FK grade 13.4–19.9 → 1.2–2.0 (textstat cross-check).

Challenges I Ran Into

Dense legal detail vs low cognitive load; paste listener that does not break form fields; three fallback layers so users are never stuck without an API key.

Accomplishments I'm Proud Of

Measured reference answers for four case studies; live AI on unseen letters with graceful fallback; comprehension and advocacy in one paste.

What I Learned

Accessible design is cognitive accessibility. A letter someone cannot read is a right they cannot use.

What's Next for Ctrl+V Access

Browser extension, local models, live Adaption Platform integration, legal-aid partnerships.

Prototype, not legal advice. Citations are starting points; verify before filing.

Built With

Share this project:

Updates

Submission history