OzWiki

Using TITLE for Accessibility

The HTML TITLE element presents a vital way for users of assistive technology to orient themselves. For example, screen readers announce the page TITLE when they load web pages. When used correctly, the TITLE element is an important tool for accessibility.

NB The TITLE element, found in the HEAD section of a web page’s HTML, should not be confused with the TITLE attribute that can be applied to most HTML elements.

You’re most likely here because you need to make sure the way you use the TITLE element on your web pages enhances accessibility for people with disabilities.

Perhaps you need a comprehensive list of likely accessibility issues with the TITLE element – and how to address them. Or maybe you just want to ask a direct question and get a clear, expert response.

You’re in the right place.

OzWiki will tell you what you need to know in order to use the TITLE element in an accessible way. The Page Title section details 7 accessibility problems and how to address them, demonstrating compliance with 6 WCAG Level A success criteria, and 1 WCAG Level AA success criterion.

As a subscriber, you’ll also be able to request further or more detailed information relating to your specific situation.

See an example

Page TITLE element is not descriptive

Page TITLE element is not descriptive

CategoryPage Title
TopicContent
WCAG SC 2.4.2: Page Titled

Web pages have titles that describe topic or purpose.

http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html

See more errors for this SC

LevelA
Technique(s)

G88: Providing descriptive titles for Web pages

ImpactHigh

Error

Some web pages do not have descriptive TITLE elements.

Incorrect Example(s)

Screenshot:Title is 'Redacted - Help'
Code:
<title>REDACTED - Help</title>

Solution

Ensure all pages have unique descriptive page title, using the TITLE element.

Already a subscriber?

Log in!

Want access?

Subscribe!

OzWiki is an accessible resource that provides best known methods to achieve A & AA level design and interaction for web content in areas such as Audio, Video, Link, Captcha, Maps, Navigation and more. These outlined accessibility errors, examples and solutions help you become 508 compliant by demonstrating associated WCAG 2.0 success criteria and techniques.

Gain access to more detailed information on all OzWiki categories for only $39/month by purchasing a subscription today! You can cancel your subscription at any time.