Research Guides
Check the Language of a Research Page, Not Just Its Translation Link
A research article can look entirely readable to its editor while giving reading software the wrong language instructions. Before distributing a report to partners or inviting others to cite it, check the language of the published page itself. A language selector in the navigation is not that check.
This is an editorial acceptance worksheet, not an accessibility certification or a promise of rankings or backlinks. It does not require buying a research service.
1. Choose a small, meaningful sample
Start with an original article, one translated version if available, and a page containing a substantial quotation in another language. Record the exact public URL and the language a reader encounters in the main text. Use real published content rather than assuming every page inherits the correct template.
For an invented example, an English competitor report includes a French paragraph quoted from a source. The report and the quotation need separate attention. A French company name alone is not a reason to relabel the entire article.
2. Inspect the default language
W3C explains that identifying a page's language helps software present its content appropriately, including screen-reader pronunciation. The underlying success criterion requires that the default human language be programmatically determinable. W3C: Language of Page
Inspect the delivered HTML and the rendered document. Note whether the opening HTML element declares a language matching the article. For a straightforward English HTML document, the familiar example is <html lang="en">. If a shared template says English on a fully French article, record the mismatch and assign the fix to that template or page configuration.
3. Review mixed-language excerpts separately
W3C's HTML guidance places the default declaration on the HTML element and explains that descendants inherit it. A surrounding element can declare a different language for a passage. The same guidance recommends valid language tags and warns against using a Content-Language meta element as the page's language declaration. W3C: Declaring language in HTML
In the invented report, inspect the French quotation's surrounding element rather than changing all the report text to French. Keep the original quotation, its translation if supplied, and its citation distinguishable. Do not imply that adding an attribute verifies the translation's accuracy.
4. Keep language, translation and discovery checks separate
Use three rows in the review record: what language the content uses, what the markup declares, and where any translation link goes. A working link does not establish that the destination is a faithful translation. Correct markup does not establish that a search engine indexed the page.
For a separate review of alternate-language page relationships, use the hreflang page-family worksheet. Do not merge its result with this narrower language check.
5. Verify the reader experience after publication
- URL and scope: record the article and passages actually reviewed.
- Before: save the observed declaration and the mismatch, if any.
- After: inspect the public response again, not only an editor preview.
- Reading test: use the assistive technology in your test plan and record the software and observed behavior.
- Limits: state whether translation quality, pronunciation and other pages remain untested.
A useful closing note is specific: “The sampled English article declares English; its French quotation has a separate declaration; reading behavior was checked in the recorded setup.” That is evidence another editor can reproduce. “The whole site is accessible and optimized for every language” is not.