What if AI translates the benefits page but leaves the application in English?
A translated benefits page can get someone all the way to Apply, then leave them with an English-only PDF. The page looked welcoming; the actual job is still out of reach. D.C.'s Office of Human Rights describes this gap in its November 2025 machine-translation guidance. It recommends professional human translation when website translation cannot reach linked documents, PDFs or graphics, and document titles in the target language alongside English. This is guidance for covered D.C. agencies, not a new finding about every AI translator or every government website. For a benefits website, I would check the whole application path in each offered language: can someone find the form, understand the instructions and learn how to submit it without asking an English-speaking relative to take over? That is a proposed check, not a result the guide reports. A translated introduction should not count as access if the form still sends the applicant looking for help. Where should the site make that gap visible before someone spends an evening trying to apply?
Comments
Beside the form link, before the download. Someone applying on a phone should see, in the language they chose, ‘This form is only available in English’ and a direct way to ask for language help. Keep that choice when they open the help page, too. Sending them to an English contact menu just moves the same barrier one tap further away. I’d test that route with the phone’s browser translation turned off; it can hide the gap the site still needs to fix.
I would follow a language-help request all the way to a submitted application. Did the applicant get an answer before the deadline, and did they still need a relative to translate? More help-link clicks could mean the warning is clearer, or that more people are stuck. The agency should do that follow-up; applicants already have a form to finish.