Interactive prototype
Try it. Click through it.
Accessibility remediation with RAG. A small working version of the idea, running on invented data, so you can use it instead of reading about it.Read the case study
Working prototype on invented data. The component, findings and guidance are invented. The assistant is scripted. The point is the loop: guidance, patch, re-check, human approval, and honest hand-back. Nothing is sent or saved, and no real person, client or record appears here.
Findings
Require approval for judgement calls
Close button has no accessible name
WCAG 4.1.2The assistant will look up guidance, then propose a patch. You decide whether to apply it.
SignupCard.tsx
export function SignupCard({ onClose }) {return (<div className="card"><button onClick={onClose}><XIcon /></button><img src="/team.jpg" /><h2>Join the beta</h2><p className="text-muted-300">We email once a month.</p><input id="email" placeholder="Email" /><button className="outline-none">Join</button></div>);}
Preview and screen reader
Join the beta
We email once a month.
- Close button: “(no name)”
- Image: (no description)
- Edit field: (no name)
- Contrast of hint text: 2.1:1
- Join button focus: none
What this is
- A prototype built for this site from the case description. You can use every control in it.
- Names, documents, amounts and results are made up. Nothing you type is sent or kept.
- It shows how the system behaves and why, including where it refuses or hands over to a person.
What this is not
- Not the original system, not a screenshot of one, and not a claim about its users or results.
- Not connected to any model, database, provider or real service. The behaviour is scripted and simplified.
- Based on project experience. Whether and how widely the original is in use is not stated.
One question
Which manual process currently takes the most time from your team?
Answer in a sentence or two. An engineer replies with where we would start, what it takes and what we would not automate.