HTML page has lang attribute


This rule applies to any document element if it is an html element that:

Note: html elements within iframe and object elements are not applicable as iframe and object elements create nested browsing contexts. However, as these elements are meant to provide a layer of isolation, the declared language of their parent browsing context will likely not be inherited, making it possible for empty lang attributes in nested browsing contexts to also cause accessibility issues.


Each test target has a lang attribute value that is neither empty ("") nor only ASCII whitespace.


The language of the page can be set by other methods than the lang attribute, for example using HTTP headers or the meta element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying Success Criterion 3.1.1: Language of Page.

Accessibility Support

There are no major accessibility support issues known for this rule.


Test Cases


Passed Example 1

This html element has a lang attribute with a non-empty ("") value.

<html lang="en"></html>


Failed Example 1

This html element does not have a lang attribute.


Failed Example 2

This html element has a lang attribute with an empty ("") value.

<html lang=""></html>

Failed Example 3

This html element has a lang attribute whose value is only ASCII whitespace.

<html lang=" "></html>

Failed Example 4

This html element has no lang attribute, only a xml:lang attribute.

<html xml:lang="en"></html>


Inapplicable Example 1

This rule does not apply to svg element.

<svg xmlns=""></svg>

Inapplicable Example 2

This rule does not apply to math element.



Attribute value

The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity.

Some notable case of attribute value, among others:

This list is not exhaustive, and only serves as an illustration for some of the most common cases.

The attribute value of an IDL attribute is the value returned on getting it. Note that when an IDL attribute reflects a content attribute, they have the same attribute value.


An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such “interim” results can be expressed with the incomplete outcome.


This section is not part of the official rule. It is populated dynamically and not accounted for in the change history or the last modified date.

Implementation Consistency Complete Report
Axe-core Consistent Yes View Report
QualWeb Consistent Yes View Report
SortSite Consistent Yes View Report


This is the first version of this ACT rule.

Back to Top