Real federal form
Social Security Disability Benefits
SSA-16 — Application for Disability Insurance Benefits
SSA-16 is an official Social Security Administration application used for Disability Insurance Benefits.
Source: U.S. Social Security Administration
AccessForce is an independent prototype. It is not affiliated with, nor endorsed by, this agency, and it never changes eligibility requirements or makes eligibility decisions.
Before
The experience people use today
- What if applying for disability benefits were designed around each person's accessibility needs from the first interaction?
AccessForce explores how AI could reduce cognitive, navigational and interaction complexity while preserving the information required by the underlying benefits process.
Disability is never the barrier. The way an experience is built is what creates one — and that is what can be redesigned.
Document preview
Representative excerptSSA-16 — Application for Disability Insurance Benefits
About you
- Full name, Social Security number, date and place of birth.
- Have you used any other names? Have you filed a previous application?
About your work and condition
- State the date you became unable to work because of your condition.
- Describe the illnesses, injuries or conditions that limit your ability to work.
- Provide dates of treatment and the names of those who treated you.
Certification
- I know that anyone who makes a false statement may be subject to penalties.
- Signature, date, mailing address and telephone number.
Short representative excerpts only — the full published document is linked above.
AXS — Accessibility Experience Score
Putting a number on the experience people face today
AXS — AccessForce Accessibility Experience Score
48 / 100
Illustrative score until audit completed
SSA-16 disability insurance benefits application
AXS weighs technical accessibility at 40%, cognitive and content accessibility at 30%, and process accessibility at 30% — so an interface that is technically operable can still score low when the process itself is hard to get through.
How AXS worksAI accessibility audit
Ask AI to examine the experience
AccessForce reads the published application the way different people would have to, and reports what may stand in their way. These are AI-identified opportunities reviewed by a person — not legal findings.
AI redesign
Let Agentforce rebuild the interaction
The eligibility rules and the systems behind them stay exactly as they are. Only the interaction changes.
After
The same service, as a conversation
Social Security Disability Benefits — assistant
Hi. I'm here to help you work through your disability benefits application. Before we start, how can I make this experience easier for you?
Before vs. after
Same public service, different experience
Before
Form-oriented
- 📄 Navigate application
- 🧠 Recall substantial information
- 🏛 Interpret terminology
- ⌨️ Fit answers into fields
- ❓ Discover assistance
After
Person-oriented
- 💬 Natural conversation
- 1️⃣ One question at a time
- 🧠 Plain language
- 🎙 Voice-ready
- ≈ Approximate answers supported
- 💾 Pause and resume
- ♿ Adaptive accessibility
- 🤖 AI organizes information
- 🙋 Human assistance available
The person shouldn't have to adapt to the form.
The experience should adapt to the person.
Measured
Before and after isn't just visible. It's measurable.
Before
48
AXS / 100
Significant OpportunitiesSSA-16 disability insurance benefits application
AccessForce redesign
After
95
AXS / 100
Highly Accessible ExperienceAdaptive Agentforce conversation over the same requirements
+0
Accessibility Experience Points
48 → 95. Illustrative score until audit completed.
Dimension by dimension
Select “Why?” on any dimension to see the finding, the recommendation and the redesign decisions the improvement is credited to.
| Dimension | Before | After | Change | Evidence |
|---|---|---|---|---|
| Visual & Perceivable | 78 out of 100 before | 96 out of 100 after | +18 | |
Severity: LowImpact area: Visual & Perceivable FindingDense pages ask people to scan long blocks of small print to find what applies to them. AccessForce recommendationPresent one question at a time, at a size and contrast the person can adjust.
Why did the score change?
| ||||
| Screen Reader & Semantic | 68 out of 100 before | 97 out of 100 after | +29 | |
Severity: MediumImpact area: Screen Reader & Semantic FindingDocument structure and field relationships are hard to follow when the experience is read aloud. AccessForce recommendationRebuild the interaction with real headings, labelled controls and a predictable reading order.
Why did the score change?
| ||||
| Motor & Keyboard | 64 out of 100 before | 96 out of 100 after | +32 | |
Severity: MediumImpact area: Motor & Keyboard FindingCompleting the experience assumes precise input and, on paper, handwriting and signatures. AccessForce recommendationMake every step keyboard-operable with large targets, and accept spoken answers.
Why did the score change?
| ||||
| Cognitive Accessibility | 36 out of 100 before | 94 out of 100 after | +58 | |
Severity: HighImpact area: Cognitive Accessibility FindingApplicants must remember substantial historical information while navigating the application. AccessForce recommendationBreak the process into smaller steps, allow approximate answers where appropriate, save unresolved information and return to it later.
Why did the score change?
| ||||
| Plain Language | 34 out of 100 before | 95 out of 100 after | +61 | |
Severity: HighImpact area: Plain Language FindingGovernment and legal terminology assumes familiarity most applicants don't have. AccessForce recommendationAsk in plain language and explain terms in place, while preserving the original meaning.
Why did the score change?
| ||||
| Process Accessibility | 30 out of 100 before | 93 out of 100 after | +63 | |
Severity: HighImpact area: Process Accessibility FindingPeople must understand the structure of the process before they can work out which parts apply to them. AccessForce recommendationLet the assistant determine the relevant path through conversational questions, and allow saving and resuming.
Why did the score change?
| ||||
| Adaptive & Personalized | 32 out of 100 before | 95 out of 100 after | +63 | |
Severity: HighImpact area: Adaptive & Personalized FindingThe experience is the same for everyone, and assistance has to be discovered before it can be used. AccessForce recommendationAsk about accessibility needs and language first, then adapt the experience to the answers.
Why did the score change?
| ||||
Illustrative score until audit completed. Each change is credited to a specific redesign decision — a score never moves simply because a conversation exists.
Why did the score change?
Process Accessibility
30 → 93+63
Why?
- Irrelevant questions removed from view
- Branching handled dynamically
- Save and resume added
- Help available throughout
- One task presented at a time
- Human escalation available
Cognitive Accessibility
36 → 94+58
Why?
- Reduced information density
- One question at a time
- Plain-language explanations
- “I don't know” supported
- Approximate answers supported where appropriate
- Follow-up items saved rather than blocking progress
Scale
One accessibility engine. Thousands of experiences.
The same audit-and-redesign engine can point at any required experience. The systems of record behind them are never replaced.
- Government
- Healthcare
- Education
- Employment
- Sports
- Travel
- Emergency Response
- Financial Services
Don't make people adapt to forms.
Make forms adapt to people.
AccessForce: Forms for All
Built for Agentforce for Good • AI Fluency Track • Type C