An activity guide → accessible, translated registration
The problem
Activity guides ship as long PDFs that residents can’t search and screen readers hear as one run of words, and staff re-key every program into the registration system.
How it's resolved
Larkhaven Parks & Recreation, a fictional city’s department. The AI reads its 16-page winter guide one page at a time and returns every session as printed. Code checks each row against the page’s own text, from the activity number to the fees, and against the calendar it implies. The AI translates each program’s name and description into Spanish, and code writes every day, time, date, age, fee and place in both languages. axe-core and code check all 28 new pages before anything publishes; the signage orange on the register button fails contrast, so code darkens it until it passes. Staff publish in bulk: 40 sessions, each with a resident and a non-resident fee on one pool of places. Then a parent registers a seven-year-old in Spanish. Code checks the age on the first day and the address against the city’s own records, the API applies the scholarship code to the resident fee only, and the places drop.
What you'll see
- 01A page of the printed guide beside what a screen reader hears from it: the heading letter by letter, then every cell as one run of words
- 02The AI reads all 16 pages: 40 sessions of 14 programs boxed on their pages, 360 fields checked against the page, and none from the pages of other tables
- 03axe-core finds the signage orange at 2.67:1 on all 28 new pages; code darkens it to 4.55:1, and the recheck finds none
- 04The new page reads row by row, in Spanish: “Actividad: 21501, Días: martes y jueves, Horario: 4:00 a 4:30 p. m.”
- 05Staff publish in bulk: 40 sessions and 28 pages, in 46 seconds of work with staff pauses aside
- 06A parent registers a seven-year-old in Spanish with a scholarship code: $48.00 becomes $24.00, the ticket is issued, and the places drop from 3 to 2
Under the hood
Each business term in the video, and the Traide building block it runs on.
| In the business | On Traide |
|---|---|
| The program page | Page, published and read by slug |
| The registration | Order with the child on its metadata; a ticket issued once paid |
| A session’s places | Capacity pool, one for both fees |
| The roster | Orders and entitlements, read by staff |
| The scholarship | Voucher for resident fees only, each code once |
| Two fees | Variants by residency |
Guardrail. Staff publish: nothing goes live from the AI alone. Code decides age and residency, and the API holds the fees, the places and the scholarship. The deadline it answers is the ADA Title II web rule: WCAG 2.1 AA by April 26, 2027 for governments serving 50,000 or more, and by April 26, 2028 for smaller ones. A test payment.
- Document understanding
- Translation
- Accessibility checks
- Eligibility checks
More demos
- Workflow orchestrationDiscovery call → priced SOW → accept and pay
- Workflow orchestrationDay-1 ready: one approval, four teams
- Product developmentA catering order by text, in the customer’s language
- Workflow orchestrationThree-way match on autopilot
- Commerce and marketplace buildsAgent-ready tours and stays
Have a problem like this one?
You'll talk to a senior engineer, not a sales rep, and leave with a clear first move — whether or not we work together.