Document title is descriptive

  • Rule Typeatomic
  • Rule ID: c4a8a4
  • Last modified: Aug 21, 2019
  • Accessibility Requirements Mapping
    • 2.4.2 Page Titled (Level: A)
      • Learn More about 2.4.2 (Page Titled)
      • Required for conformance to WCAG 2.0 and above on level A and above
      • Outcome mapping:
        • Any failed outcomes: not satisfied
        • All passed outcomes: further testing is needed
        • An inapplicable outcome: further testing is needed
  • Input Aspects

Description

This rule checks that the document title describes the topic or purpose of the document.

Applicability

This rule applies to the first HTML title element that

Expectation

The target element describes the topic or purpose of the overall content of the document.

Assumptions

There are no assumptions for this rule.

Accessibility Support

  • This rule assumes that browsers only recognize the first title element if multiple title elements are present in the document. Testing shows that this in general is the case. Therefore the scope of this rule is limited to only checking the first title element in a document.

Background

Test Cases

Passed

Passed Example 1

The <title> element describes the content of the document.

<html>
	<head>
		<title>Clementine harvesting season</title>
	</head>
	<body>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Passed Example 2

Two <title> elements where the first one describes the content of the document.

<html>
	<head>
		<title>Clementine harvesting season</title>
		<title>Second title is ignored</title>
	</head>
	<body>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Passed Example 3

Even though the descriptive <title> element is not placed within the <head> element that is the context the element can be used in according to the HTML specification, the rule still passes, since the browser fixes it, and it doesn't cause any known accessibility issues.

<html>
	<head> </head>
	<body>
		<title>Clementine harvesting season</title>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Passed Example 4

<title> element with content present in document, and the title is descriptive of the content, even though it does not contain letters or numbers.

<html>
	<head>
		<title>;)</title>
	</head>
	<body>
		<h1>;)</h1>
		<p>
			The winking emoticon is commonly used after a light-hearted or sarcastic remark. It is also a popular IM and
			e-mail emoticon shortcut.
		</p>
	</body>
</html>

Failed

Failed Example 1

<title> is not descriptive of the content of the document.

<html>
	<head>
		<title>Apple harvesting season</title>
	</head>
	<body>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Failed Example 2

Even though a correct <title> element is put in the <head> of the document, this rule only looks at the first <title> element.

<html>
	<head>
		<title>First title is incorrect</title>
		<title>Clementine harvesting season</title>
	</head>
	<body>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Failed Example 3

<title> element with content present in document, but it is not descriptive of the content.

<html>
	<head>
		<title>;)</title>
	</head>
	<body>
		<p>
			Clementines will be ready to harvest from late October through February.
		</p>
	</body>
</html>

Inapplicable

Inapplicable Example 1

This document has a <title> element but is inapplicable since the document element is an SVG <svg> element.

<svg xmlns="http://www.w3.org/2000/svg">
  <title>This is a circle</title>
  <circle cx="150" cy="75" r="50" fill="green"></circle>
</svg>

Glossary

Outcome

key: outcome

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:

  • Inapplicable: No part of the test subject matches the applicability
  • Passed: A test target meets all expectations
  • Failed: A test target does not meet all expectations

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: Implementers 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.

Whitespace

key: whitespace

Characters that have the Unicode "White_Space" property in the Unicode properties list.

This includes:

  • all characters in the Unicode Separator categories, and
  • the following characters in the Other, Control category:

    • Character tabulation (U+0009)
    • Line Feed (LF) (U+000A)
    • Line Tabulation (U+000B)
    • Form Feed (FF) (U+000C)
    • Carriage Return (CR) (U+000D)
    • Next Line (NEL) (U+0085)

Changelog

Aug 21, 2019Editorial changes (#725)
Jul 19, 2019chore: run prettier (#688)
Jun 25, 2019Map pass to satisfied on document title rule (#606)
Jun 21, 2019fix: Make "manual" rules consistent with their SC (#586)
May 29, 2019chore: add missing contributors (#572)
May 18, 2019chore: Validating rules frontmatter on CI (#551)
May 9, 2019Chore: Adapt site to ACT Rules CR format (#547)
May 7, 2019Template update - Document title is descriptive (#506)
May 2, 2019chore: add manual reporting download links to rule (#492)
Apr 26, 2019chore: Add id to document-title-is-descriptive rule (#491)
Apr 26, 2019New rule: Document title is descriptive (#380)

Useful Links


Implementations

Tool NameCreated ByReport

Acknowledgements