Skip to content
Pandus

WCAG A/AA requirement Priority: Serious

The page's language setting is wrong

The page declares a language code that does not exist, for example a typo or a made-up value.

This text was translated automatically and has not been reviewed by a native speaker yet.

Why it matters to your customers

Assistive technology cannot use the code, so text may be read with the wrong pronunciation. Translation tools may also misidentify the language.

Who is affected

  • blind customers
  • screen reader users
  • people who use read-aloud or translation tools

How to fix it

Use a valid BCP 47 language code in <html lang>, such as "en", "de", "pl", "uk" or "de-AT". Check for typos, underscores (use "de-DE", not "de_DE") and empty values. Make sure each language version outputs its own correct code.

On Shopify

Usually caused by a custom edit in the theme's layout file or a translation app. Check the value printed in the <html> tag and correct it in the layout Liquid file or the app's settings.

On Shoptet (CZ)

Usually comes from the shop's language settings or a template customisation. Check the language configuration first, then ask Shoptet or a partner about the template.

On PrestaShop

Check the language ISO code configured for each shop language in the back office and any hard-coded value in the theme's layout template.

On WooCommerce

Usually caused by a misconfigured site language, a multilingual plugin or a hard-coded value in the theme header. Check WordPress language settings and the multilingual plugin first.

Standards

Standards
StandardClause
WCAG 2.2 3.1.1 (A) Language of Page
WCAG 2.1 3.1.1 (A) Language of Page
WCAG 2.0 3.1.1 (A) Language of Page
EN 301 549 4.1.1 9.3.1.1
EN 301 549 3.2.1 9.3.1.1
Section 508 2017 E205.4
ДСТУ EN 301 549 2022 9.3.1.1

Automated check: axe-core rule html-lang-valid. dequeuniversity.com, github.com, www.w3.org

All rules we check