Skip to main content
AccessForce
Text size: 100 percent

Multilingual access

Every form. Every person. Every language.

Language should never be the reason someone can't get help from their government. In AccessForce, language comes first — and the meaning travels with it.

Choose a language before anything else

The language question comes first — before the first form question, not buried in a footer.

Other — tell AccessForce which language you'd like

English — English

Hi! I'm here to help you complete your application.

How would you like me to help?

How many people live in your home, including you?

  • Just me
  • 2 people
  • 3 people
  • 4 or more

Why are you asking?

100+ languages

“100+ languages” describes where this approach is heading. This prototype demonstrates a curated set, and any production deployment would confirm coverage with the agency's own language-access policy.

The language covers everything, not just the questions

  • questions
  • explanations
  • help text
  • accessibility settings
  • error messages
  • document requests
  • progress updates
  • AI responses
  • follow-up questions
  • human escalation instructions

Semantic transformation

Translation is not enough.

Traditional translation usually means converting a static form word for word. The sentence changes language, but it stays just as hard to understand — and the person still has to work out what the agency actually wants.

  1. Stage 1 — Government requirement

    “Provide the aggregate household income received during the applicable reporting period.”

    The wording the source process uses.

  2. Stage 2 — Plain English

    “How much money does everyone in your household usually receive each month?”

    Same requirement, everyday words.

  3. Stage 3 — Español

    “¿Cuánto dinero recibe normalmente cada mes su hogar en total?”

    The meaning is translated, not the sentence structure.

What happens between the stages

  1. 1Understand the underlying requirement.
  2. 2Convert it into plain language.
  3. 3Translate the meaning.
  4. 4Preserve the required government data.
  5. 5Let the resident answer naturally.
  6. 6Convert the answer back into structured data.

Two-way conversation

People answer in their own words. The agency receives structured data.

¿Cuánto dinero recibe normalmente cada mes su hogar en total?

Trabajo unas 25 horas por semana y gano aproximadamente $1,700 al mes.

¿Cuánto paga de vivienda cada mes, incluyendo los servicios?

The follow-up question is generated in Spanish too — the conversation never drops back into English.

Switching language midway

Someone can change language at any step. Nothing restarts, nothing is lost.

Your progress is saved. You can continue in Spanish.

Try switching language in the experience

The translation burden

Today, every language means another document to maintain.

Today: translate every form

  1. 1Form changes
  2. 2Translate English PDF
  3. 3Spanish translation
  4. 4Chinese translation
  5. 5Vietnamese translation
  6. 6Arabic translation
  7. 7Review each version
  8. 8Publish each version
  9. 9Repeat whenever the source form changes

With AccessForce

  1. 1Maintain one authoritative source process
  2. 2AccessForce understands the intent and the required data
  3. 3Generate accessible multilingual experiences dynamically

Update the source once.

Improve every language experience.

This does not remove required legal or professional translation review. Agencies can combine AI-assisted translation with human review, approved terminology and existing language-access policies.

Language governance

The agency stays in control of every word.

A configuration surface an agency's language-access team would own — not a black box.

  • ApprovedSigned off by the agency and safe to publish.
  • AI generatedDrafted by AI and waiting for a reviewer.
  • Human reviewedChecked by a bilingual reviewer or vendor.
  • Needs reviewChanged since last approval, or flagged by a reviewer.

Approved translations

Approved

A reviewed translation is locked in and reused wherever that requirement appears.

“Household” → “hogar” (Spanish), reviewed 12 Aug

Agency terminology

Approved

The agency's own glossary takes priority over anything AI would choose.

“Medical Assistance”, not “health insurance”

Prohibited translations

Human reviewed

Wordings a reviewer has ruled out stay out of every language experience.

Never render “benefit” as “beneficio social”

Legal phrases that must stay exact

Approved

Certification, perjury and appeal-rights language is shown verbatim, with a plain-language explanation beside it.

Penalty-of-perjury certification, unchanged

Program names that are not translated

Approved

Official program names stay recognisable so people can match them to letters and websites.

“SNAP”, “Medicare Part B”, “CalFresh”

Preferred reading level

Approved

The agency sets the target reading level for each language experience.

Grade 6 target, per state plain-language policy

Culturally appropriate terminology

AI generated

Reviewers can adjust wording that is technically correct but unfamiliar to the community being served.

Regional wording for “household” in Vietnamese

Human-review requirements

Approved

Which content types must be reviewed by a person before they can be published.

All eligibility and appeal content

Languages requiring certified translation review

Needs review

Languages where a certified translator must sign off, per agency or state policy.

Arabic, Somali — certified review required

AI drafts. Reviewers approve. The agency's terminology always wins.

Support cost

Most multilingual phone calls are navigation questions.

Many agencies rely on multilingual call centers, interpretation services and specialized staff because residents struggle to navigate forms and digital processes on their own. AccessForce can help agencies shift routine translation and form-navigation questions toward self-service while preserving multilingual human support for complex situations.

Today

  1. 1Resident doesn't understand form
  2. 2Calls agency
  3. 3Waits for agent
  4. 4Language identification
  5. 5Bilingual agent or interpreter
  6. 6Agent explains question
  7. 7Resident completes form
  8. 8Calls again when another issue occurs

With AccessForce

  1. 1Resident selects preferred language.
  2. 2AI guides the resident through the process.
  3. 3Human support is available when needed.

Use expensive human support where humans add the most value.

See the projected agency impact

Multilingual AXS

AXS by language

Accessibility should be measured in every language — not just English.

  • English

    English

    91

    AXS out of 100 — illustrative

  • Spanish

    Español

    88

    AXS out of 100 — illustrative

  • Chinese

    中文

    84

    AXS out of 100 — illustrative

  • Vietnamese

    Tiếng Việt

    79

    AXS out of 100 — illustrative

Illustrative prototype comparison, generated for demonstration. Not a compliance certification.

Forms for All. Languages for All. Services for All.

Don't make people adapt to forms. Make forms adapt to people — in the language they actually speak.

Try the experienceSee AccessForce Insights