Watching your screen reader stumble through a translated webpage is frustrating. If Chrome translate accessibility issues are breaking your workflow, the fastest fix is disabling auto-translate in chrome://settings/languages and using manual translation instead. Chrome’s built-in translator modifies DOM structure without updating accessibility trees, causing screen readers to lose focus and miss content updates.

This article covers the technical reasons behind translation accessibility conflicts, four manual fixes ordered by effectiveness, and a permanent solution using BeLikeNative that maintains accessibility while translating content.

The fastest fix: Open chrome://settings/languages, scroll to Translation, and turn off “Offer to translate pages that aren’t in a language you read.”

Why Chrome Translation Causing Accessibility Issues

Chrome’s translation system creates three specific accessibility problems that affect screen readers and keyboard navigation.

DOM Modification Without Accessibility Updates

Chrome’s Translator API rebuilds page content during translation but doesn’t update ARIA labels or accessibility trees. When translation happens, the original DOM nodes get replaced with translated versions. Screen readers that were tracking specific elements lose their reference points.

The browser downloads translation models locally the first time a website uses this API, then modifies text content in real-time. However, this process doesn’t preserve accessibility attributes like aria-label, aria-describedby, or role assignments that screen readers depend on.

“The Translator API allows you to translate text with AI models provided in the browser. The model is downloaded the first time a website uses this API.” , Translation with built-in AI - Chrome Translator API

Focus Management Breaks During Translation

Chrome’s translation process interrupts keyboard navigation by resetting focus to the document body. If you’re tabbing through a form or navigating with arrow keys, translation triggers cause focus to jump unexpectedly.

This happens because Chrome rebuilds the translated content as new DOM elements. Your focus position on the original element becomes invalid when that element gets replaced. Screen readers lose track of where users were reading, forcing them to start navigation over.

Language Detection Conflicts With Screen Reader Language

Chrome’s automatic language detection can override screen reader language settings. When Chrome detects content in one language but your screen reader expects another, pronunciation and navigation commands become unreliable.

Screen readers use language information to determine pronunciation rules and keyboard shortcuts. If Chrome changes the page language during translation without notifying assistive technology, screen readers continue using the wrong language rules.

“The Intl object is the namespace for the ECMAScript Internationalization API, which provides locale-sensitive string comparison, number formatting, and date/time formatting.” , Internationalization (Intl) - JavaScript - MDN Web Docs

How to Fix Chrome Translation Causing Accessibility Issues

These four fixes address translation accessibility problems, ordered from most to least effective. Each includes exact steps and expected results.

Disable Auto-Translation Completely

The most reliable fix prevents Chrome from automatically translating pages. Open Settings → Advanced → Languages → Language. Under “Translation,” turn off “Offer to translate pages that aren’t in a language you read.”

This stops Chrome from modifying page content without user permission. You can still translate manually by right-clicking any page and selecting “Translate to English” (or your preferred language). Manual translation gives you control over when DOM changes happen.

Trade-off: You’ll need to manually request translation for each foreign language page. However, this gives screen reader users time to prepare for content changes.

Configure Translation Language Preferences

Set up specific language pairs to reduce unexpected translation prompts. In chrome://settings/languages, click “Language” then “Add languages.” Add languages you read fluently to prevent Chrome from offering translation for content in those languages.

For each language you add, click the three-dot menu and select “Offer to translate pages in this language” to disable translation offers. This approach works well if you regularly visit content in 2-3 specific languages.

Expected result: Chrome will only prompt translation for languages not in your approved list. This reduces interruptions while maintaining translation access for truly foreign content.

Use Chrome’s Accessibility Features

Enable Chrome’s built-in accessibility options that work better with translation. Go to chrome://settings/accessibility and turn on “Live Caption” and “Focus highlighting.” These features maintain better compatibility during translation events.

Live Caption provides text alternatives that don’t rely on DOM content, so translation changes won’t break caption functionality. Focus highlighting makes keyboard navigation visible during translation transitions.

Press Ctrl+Shift+A (Windows) or Cmd+Shift+A (Mac) to open accessibility settings quickly. Enable “Tab navigation” to improve focus management during content changes.

Install Translation Extensions With Accessibility Support

Replace Chrome’s built-in translation with extensions designed for accessibility compatibility. Look for extensions that preserve ARIA attributes and maintain focus during translation.

Extensions that translate content in overlays or side panels avoid modifying the original page DOM. This prevents screen readers from losing track of page structure and navigation state.

However, extension-based solutions require trusting third-party developers with page content and may have performance impacts compared to Chrome’s native translation system.

Fix It Permanently with BeLikeNative

Manual fixes work but require constant attention to translation settings and language configurations. BeLikeNative handles translation differently by preserving accessibility attributes during content modification.

Unlike Chrome’s built-in translator that rebuilds DOM content, BeLikeNative translates text while maintaining original ARIA labels and focus management. The extension uses Chrome’s i18n API to handle multiple languages without breaking screen reader navigation.

“Use the chrome.i18n infrastructure to implement internationalization across your whole extension, providing locale-specific strings via messages.json files.” , chrome.i18n API - Chrome Extensions

BeLikeNative’s 4.6-star rating reflects its focus on accessibility-first translation. The extension translates content in place while preserving keyboard navigation state and screen reader context. Version 1.4.8 includes specific improvements for ARIA compatibility and focus management during translation events.

The 999KiB extension size keeps memory usage minimal while providing comprehensive translation coverage. BeLikeNative works as a paraphrase and rewrite tool as well, giving you translation options that maintain accessibility without switching between multiple tools.

Try BeLikeNative Free

FAQ

Does disabling Chrome translation break Google Translate?

No. Google Translate in a separate browser tab continues working normally. Only Chrome’s automatic page translation gets disabled, which actually improves compatibility with screen readers and other assistive technology.

Can I re-enable translation for specific websites?

Yes. Right-click any page and select “Translate to English” for manual translation. Chrome also lets you set per-site translation preferences in chrome://settings/content/all by searching for specific domains.

Why don’t other browsers have these accessibility issues?

Firefox and Safari handle translation differently. Firefox uses separate translation overlays that don’t modify original page content. Safari’s translation system better preserves accessibility attributes during content modification, though both browsers have fewer translation features than Chrome.

Built by Michael Lip. More tips at zovo.one.