Office Compatibility Issues

How to Fix JAWS Reading Word Content Control Text in the Wrong Language

Ayan MasoodAyan Masood Oct 28, 2026 870 views

Question details

The user needs to resolve an issue where the JAWS screen reader incorrectly pronounces foreign language text as English when it is located inside a Microsoft Word plain-text content control.

How to Fix JAWS Reading Word Content Control Text in the Wrong Language
Product
Microsoft Word
Device & OS
not provided
Scenario
Using third-party screen readers to read localized or multilingual text embedded within plain-text content controls in a Word document.
Observed behavior
JAWS ignores the specific proofing language applied to the text inside the content control and reads it with English pronunciation, whereas Word's native Read Aloud feature pronounces it correctly.
Before you start

Ensure that the proofing language for the specific text is correctly set to your target language in Word, and verify that your screen reading software is updated to the latest available version.

Solution 1Recommended

Use Word Read Aloud or Windows Narrator

Since third-party screen readers have known limitations with Word content controls, utilizing Microsoft's native accessibility tools provides an immediate and accurate workaround.

Third-party screen readers like JAWS and NVDA often struggle to detect language attributes embedded within Word's content control structures. Microsoft's built-in tools integrate natively with these elements and successfully recognize the applied proofing language.

1
Select the text

Click inside the plain-text content control that contains the text you want to read.

2
Activate Word Read Aloud

Navigate to the 'Review' tab on the Word ribbon and click 'Read Aloud', or use the keyboard shortcut Alt + Ctrl + Space.

3
Switch to Windows Narrator

If you prefer a system-wide screen reader, press the Windows logo key + Ctrl + Enter to launch Windows Narrator, which processes Word content controls correctly.

Use Word Read Aloud or Windows Narrator
Native Integration: Word's Read Aloud feature seamlessly detects the exact proofing language inside content controls, ensuring correct pronunciation.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Compatibility

If you are frustrated by specific bugs, accessibility limitations, or complex content control behaviors in Microsoft Word, consider switching to WPS Office. It is a lightweight, highly compatible alternative designed to handle your everyday document editing needs smoothly.

  1. 1. Download the software: Visit the official WPS website and download the free WPS Office installer for your operating system.
  2. 2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the suite.
  3. 3. Open your documents: Launch WPS Writer and open your existing Word documents to continue editing with full format compatibility.
Fully compatible with Microsoft Word document formats (.docx, .doc).Free and lightweight, ensuring stable performance on lower-end devices.Clean, familiar user interface allowing for an immediate and seamless migration.Simplifies document editing without the heavy overhead of complex legacy controls.
microsoft office alternative - wps office

Frequently Asked Questions

Why does JAWS mispronounce French text in Word content controls?

Third-party screen readers like JAWS and NVDA currently have known accessibility limitations when interacting with plain-text content controls in Microsoft Word. They fail to parse the specific language tags applied inside the control, defaulting to the system's primary language.

Can I fix the language issue by changing Word's default proofing language?

Changing the default proofing language typically does not resolve this specific issue. The problem lies in how the screen reader software interacts with the content control's underlying code, not the document's overall language setting.

Does NVDA have the same reading issue with Word content controls?

Yes, similar accessibility limitations have been reported with NVDA. Using Microsoft's native Narrator or the built-in Read Aloud feature in Word is currently the most reliable workaround for both screen readers.

Is there a way to make the document accessible without using Read Aloud?

If your document heavily relies on third-party screen readers, consider removing the content controls and using standard formatted text instead. Standard text elements reliably pass proofing language metadata to JAWS and NVDA.