Architectural Blueprint And Strategic Implementation For The Who Cares Wizard On 2Ia - Source Excerpt 05 - Accessibility and localization

Back to Architectural Blueprint And Strategic Implementation For The Who Cares Wizard On 2Ia

Summary

This source excerpt begins near Accessibility and localization and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-17-who-cares-wizard/Architectural Blueprint and Strategic Implementation for the Who Cares Wizard on 2ia.org.md.

**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-17-who-cares-wizard/Architectural Blueprint and Strategic Implementation for the Who Cares Wizard on 2ia.org.md

| UX pattern | Implementation note | Why it matters |
|---|---|---|
| One question per screen | Keep choices short, with plain-language helper text and “why we ask this” disclosure | Reduces cognitive load and preserves emotional focus |
| Persistent help control | Keep “Need help now?” in the same relative position on every step | Matches WCAG 2.2 consistent-help expectations citeturn17view0 |
| Large touch targets | Keep tap targets at least 24 by 24 CSS pixels or provide enough spacing | Matches WCAG 2.2 target-size guidance citeturn17view0 |
| No drag-only actions | All reordering or navigation must have a simple pointer alternative | Matches WCAG 2.2 dragging-movements guidance citeturn17view0 |
| Strong focus visibility | Never let sticky headers, banners, or modals obscure focus | Matches WCAG 2.2 focus-not-obscured guidance citeturn11view0turn17view0 |
| Minimal repeated entry | Reuse previously provided information inside the same session | Matches WCAG 2.2 redundant-entry guidance citeturn17view0 |
| Accessible authentication if save/resume exists | Prefer passwordless magic links or passkeys; allow paste and password managers | Matches WCAG 2.2 accessible-authentication guidance citeturn17view0 |
| Quick exit and no-save mode | Prominent but discreet escape action, especially in abuse branches | Supported by survivor tech-safety guidance citeturn24search0turn24search1 |
| Multi-channel results | Show “Call,” “Text,” “Chat,” and “Website” where available | Important because official services vary by channel and access mode citeturn23search0turn3search1turn3search2 |

If the wizard ever serves a public-sector or government-adjacent deployment, the 2024 DOJ Title II rule is highly relevant because it concretely ties public web and mobile accessibility to WCAG 2.1 AA. Even for a private deployment, that is a useful legal-grade benchmark. WCAG 2.2 extends that baseline with improvements especially relevant to forms, support placement, touch input, and authentication. citeturn11view5turn11view0turn17view0

### Accessibility and localization

Localization should be treated as a structural concern, not a translation afterthought. W3C’s internationalization guidance recommends using **UTF-8 throughout**, supporting local name/address/date formats, declaring page language with the `lang` attribute, and using `dir="rtl"` when needed for right-to-left languages. W3C also stresses that internationalization means designing the system to adapt across cultures, scripts, and formats, not merely swapping strings. citeturn14view1turn14view3turn13search2

For this product, that implies:

- a visible language switcher on every page;
- externalized strings and locale-aware date and address handling;
- structured support for English, Spanish, and right-to-left scripts as early targets;
- resource cards filtered by **language** and **accessibility channel**;
- no text baked into images;
- readable plain-language copy with culturally neutral examples.

Those choices align with the reality of the services themselves. The National Domestic Violence Hotline supports live advocates and interpretation across hundreds of languages, 988 offers Spanish services and Deaf/Hard of Hearing pathways including ASL videophone and TTY relay guidance, and HUD housing counseling can be accessed in a variety of languages. The wizard should therefore ask about language and communication preference early enough to influence ranking instead of treating those as afterthoughts. citeturn3search9turn23search0turn23search2turn23search6turn4search4

### Sample UI question screens

' ' ' text
Who Cares Wizard
Step 1 of 5

Are you or someone else in immediate danger right now?

( ) Yes, right now
( ) Urgent help is needed today
( ) No immediate danger

[Continue]   [Quick exit]
Need help now? Call, text, or chat options
' ' ' 

' ' ' text
Who Cares Wizard
Step 2 of 5

What best describes the issue?

[ Safety or abuse ]
[ Housing or utilities ]
[ Health, disability, or caregiving ]
[ Work, money, debt, or benefits ]
[ Child, youth, or family ]
[ Discrimination, immigration, or legal status ]
[ Environment, disaster, or public services ]

[Back] [Continue]
' ' ' 

' ' ' text
Who Cares Wizard
Results

Primary route: Housing counselor and eviction support
Why this was chosen:
- You said eviction is likely within 7 days
- You are not looking for shelter tonight
- You want rights and negotiation help first

Start here
[ Call / Chat / Open official site ]

Also consider
- Fair housing complaint path
- Free legal aid near you

Before you go
[ Download summary ] [ Share selected fields ] [ Start over ]
' ' ' 

### Sample response templates and next-step actions

**Emergency response template**

> **Get help now.** You told us someone may be in immediate danger. Skip the rest of the questionnaire. Use one of the crisis options below now.  
> **Next actions:** choose call/text/chat; confirm your location; choose language or accessibility support; if safe, return later for ongoing support resources.

**Official complaint route template**

> **Best first route: file or prepare an official report.** Your answers suggest this problem is time-sensitive and handled by an official agency.  
> **Why this route fits:** you reported a recent incident, a likely legal or administrative deadline, and a category with a formal complaint pathway.  
> **Next actions:** gather dates, notices, screenshots, letters, worksite or landlord details; open the official complaint page; if you want, also contact legal aid.

**Service-navigation template**

> **Best first route: service locator and human support.** Your answers suggest you need access to a service more than a formal complaint.  
> **Why this route fits:** you reported a need for housing, care, treatment, or benefits rather than enforcement first.  
> **Next actions:** search nearby providers; choose the safest contact method; save your result; ask for language or disability accommodations when contacting the provider.

**Ambiguous or multi-system route template**

> **You may need more than one system.** Your answers suggest this problem overlaps more than one area.  
> **Primary route:** the first place most likely to help immediately.  
> **Secondary route:** the agency or legal-support option for rights or accountability.  
> **Next actions:** start with the primary route today; use the secondary route if the first system cannot act or if you need to file a complaint.

### Metrics to evaluate effectiveness

The product should be evaluated on **safety, routing quality, user trust, accessibility, and outcomes**, not just completion rate.

| Metric | What it measures | Healthy direction |
|---|---|---|
| Safety interrupt precision | Whether high-risk users are interrupted promptly without false reassurance | High |
| Time to first actionable result | Seconds from entry to first usable route | Low |
| Completion rate by branch | Whether ordinary users can finish without dropping off | High |
| Abandonment rate before first route | Whether the interview is too long or confusing | Low |
| Route acceptance rate | Whether users click or use the primary route shown | High |
| Fallback-route usage | Whether primary routes are too narrow or confidence is low | Moderate but stable |
| User-reported relevance | “Did this help you find the right place?” | High |
| Confirmed handoff rate | Whether users actually reached a provider, regulator, or aid channel | High |
| Misroute rate | Cases where a human review or follow-up shows the route was wrong | Low |
| Repeat-use rate for unresolved cases | Whether users return because first routing failed | Low to moderate |
| Screen-reader and keyboard success rate | Accessibility of the interactive flow | High |
| Language-switch success rate | Whether multilingual users find and use localized content | High |
| Anonymous-mode usage | Whether privacy-aware users still feel safe using the tool | Measured, not “maximized” |
| Opt-in share rate | Whether users trust field-level sharing enough to hand off data | Moderate to high |
| Privacy/security incident count | Breaches, misdirected sharing, unauthorized retention | Zero |

The analytics design should itself be privacy-conservative. Aggregate event telemetry is enough for most product learning. Raw grievance text should not be retained by default, and any content-level review workflow should be explicitly consented and tightly controlled.

### Recommended final product stance

The best strategic framing for the Who Cares Wizard is this:

- It is **not** a generic help center.
- It is **not** a legal-advice engine.
- It is **not** a crisis service pretending to replace crisis services.