When content on a page uses a language different from the default, what should be possible according to Trusted Tester guidelines?

• A. The language of content can be programmatically determined.
• B. The language cannot be determined.
• C. The content must be in the same language as the default.
• D. The language must be declared only in a dedicated language file.

Answer: (A)

The important idea is that multilingual content should expose its language in a way that software can detect it. When a page includes text in a language different from the default, Trusted Tester guidelines expect that the language of that content can be determined programmatically. This is usually done by marking the language with standard attributes in the markup (for example, language codes on the relevant elements or page) so assistive technologies like screen readers and other tools can adjust pronunciation, reading rules, and formatting accordingly. This ensures users hear and perceive the text correctly, and it helps with correct indexing and potential translation workflows.

If the language couldn’t be determined, screen readers might mispronounce words, treat localized numbers or dates incorrectly, or fail to switch to the appropriate pronunciation rules. Requiring all content to match the default language ignores legitimate multilingual content and reduces accessibility. Requiring language information to be declared only in a separate language file would miss per-element variations and inline content, making it harder to maintain and less reliable for users who rely on accurate language cues.