Why Does My Website Need to Declare Its Language? The One-Line Accessibility Fix
If your audit flagged "page language not declared," it caught something no sighted visitor will ever notice, because it changes nothing about how your page looks. It's a single missing word in the very first line of your page's code, and it's the most basic accessibility requirement there is - the one every other accessibility rule assumes is already true.
What the language declaration actually is
Every HTML page opens with an <html> tag, and that tag can carry a lang attribute naming the page's language: <html lang="en"> for English, lang="es" for Spanish, and so on. It's metadata, not content - nothing about it renders on the page. It exists purely so that software reading the page (a screen reader, a browser's translate feature, a search engine) knows what language it's looking at instead of having to guess.
<html> - no language declared at all
<html lang="en"> - every tool reading the page now knows it's English
Why a screen reader actually cares
Screen readers don't just read text out loud - they switch pronunciation engines and accents based on declared language, because the same letters are pronounced completely differently in different languages. Without a declaration, the screen reader falls back to a default, and for a visitor using a different default language on their own device, that default can be wrong. The result is English text read aloud with the pronunciation rules of another language entirely - technically "read," but close to unintelligible. This is exactly the kind of defect a sighted developer will never catch by looking at the page, because looking at the page is not how the problem shows up.
It also confuses translation tools
Browser-built translation features (Chrome's offer to translate a page, for example) detect a page's source language partly from this same attribute. A missing or wrong declaration can mean the browser doesn't offer to translate at all for a visitor who doesn't read English, or mis-detects the language and produces a worse translation than it otherwise would have. For a local business whose customer base includes non-English speakers, that's a real, if invisible, piece of lost reach.
Not the same thing as hreflang tags
It's easy to conflate this with hreflang tags, which tell Google which translated version of a page to show a searcher in a given region - but they solve different problems. The lang attribute describes the one page currently loaded, for accessibility tools and translation. hreflang only matters once a site actually has multiple language versions of the same page to choose between. A single-language small business site needs the lang attribute; it almost never needs hreflang.
Why this is the most basic accessibility rule there is
The Web Content Accessibility Guidelines list "Language of Page" as one of their Level A success criteria - the baseline tier, below which a site isn't just falling short of best practice, it's failing the fundamentals. Every other accessibility technique - correct link text, working accessible names, readable color contrast - assumes a screen reader can already parse and pronounce the text correctly. A missing language declaration undermines that assumption before any of the other fixes even get a chance to help.
How to check your own site in under a minute
Right-click near the top of any page and choose "View Page Source" (or press Ctrl/Cmd+U). Look at the very first line of the file: <html lang="...">. If lang is missing entirely, or set to a language your page isn't actually written in, that's the defect.
How to fix it
Add lang="en" (or the correct two-letter code for your site's actual language) to the opening <html> tag. Because this tag lives in the page template or theme header rather than in individual page content, it's usually a single edit that fixes every page on the site at once, not something that has to be repeated page by page.
How the free audit catches this
A missing or incorrect language declaration is one of the checks in our free audit, run alongside speed, SEO, and the rest of our website audit checklist. It comes back as a medium-impact accessibility finding, the same category that also covers contrast, accessible names, and the other basics covered in our ADA compliance post.
Frequently asked questions
What does the html lang attribute actually do?
It's a one-word declaration in the opening <html> tag - <html lang="en"> - that tells browsers, screen readers, and search engines what human language the page's text is written in. Nothing about how the page looks changes; it's metadata a machine reads, not something a sighted visitor ever sees.
What actually breaks if it's missing?
A screen reader has to guess which language's pronunciation rules to use, and it usually guesses wrong for at least some visitors - reading English text with a different language's text-to-speech voice, mangling every word. Browser translation tools also rely on this attribute to detect the source language, so a missing or wrong declaration can make auto-translate misfire or not offer to translate at all.
Is this the same thing as hreflang tags for multi-language sites?
No, they solve different problems. The html lang attribute declares the language of the one page currently loaded, for accessibility tools and translation. hreflang tags tell Google which alternate-language version of a page to show searchers in different regions. A single-language small business site only needs the lang attribute - hreflang only matters once you have multiple translated versions of the same page.
How do I fix a missing language declaration?
Add lang="en" (or the correct two-letter code for your site's language) to the opening <html> tag on every page template. It's a single attribute, usually a one-line change in whatever template or theme file controls the page's head, and it applies site-wide instead of needing to be repeated per page.
How do I check my own site for this?
View the page source (or right-click near the top of the page and choose View Page Source) and look at the very first line: <html lang="...">. If the lang attribute is missing entirely, or set to the wrong language, that's the defect. Our free audit checks this automatically on the page you submit.
The cheapest way to find out
Run the free audit below. We check the language declaration along with speed, SEO, and the rest of accessibility, using the same tooling Google itself uses, and email you a plain-English report naming exactly what's missing. If something needs fixing, it's a flat $149 for your fixable speed/image/SEO/broken-link issue, or $299 for everything, with before-and-after proof once it's done.