As useful as
<span> elements can be as generic containers, they’re not always the most a11y friendly elements to use. While it may be tempting or easier to just use them for everything, from containers to interactive areas, you should not only check whether there is a more appropriate element to use in certain situations, but also whether you’re using an element correctly.
This section contains a general overview of topics that you will learn in this lesson.
- Explain why semantic HTML is important for accessibility.
- Name the seven HTML elements that define landmarks on a page.
In terms of web accessibility, using semantic HTML is important because it provides meaning and context. Some elements have a semantic meaning, but don’t really provide any context when announced by assistive technologies, such as the
<p> element. Then there are elements that have a semantic meaning and are announced with some sort of context to help users perceive or operate them, like a
<span> elements, most likely two of the more common elements you use, are semantically neutral. That is, they themselves have no semantic meaning and provide no context on their own to assistive technologies, which can make it more difficult for users of such technologies to perceive, operate, and understand them. Don’t let this lack of semantics and context make you feel like you can never use a
<span> ever again, though. They still have their uses as generic containers, such as for layouts or for generic text.
Okay, let’s look at an actual example to help better understand this whole semantics and context thing. Think of any project you may have completed so far that required a user to click on something: Rock, Paper, Scissors; Calculator; Tic-Tac-Toe. If you used
<span> elements for any clickable areas, things most likely worked as intended for you. For example, perhaps you had something similar to the HTML below for your Rock, Paper, Scissors UI back in Foundations:
<!-- These are buttons... right? -->
A sighted user would most likely have no trouble playing the game if the elements looked like something to interact with. A screen reader user, however, would have no idea what any of these elements mean. The screen reader would announce the text contents of the element (“Rock”, “Paper”, or “Scissors”), and the user might think it’s just plain text on the page and move on. There’s no context to tell the user that they’re supposed to, or that they even can, interact with these elements.
This issue can be easily fixed by using semantic HTML:
<!-- Okay, these are *definitely* buttons -->
<button> element has a semantic meaning and provides context, a screen reader would announce the text content as well as the role of the element: “Rock, button”.
Using semantic HTML correctly
When it comes to using semantic HTML correctly, you want to think about what your intent for users is and what context you want (or need) to provide to them. This can vary depending on the situation, but there are some things you should absolutely be checking for moving forward:
- If a user is meant to click something, whether it’s an actual button or not, you will usually want to use a
<button>element. This will let the user know that they can interact with the element by clicking on it.
- If you want to provide some sort of tabular data to a user, use a
<table>element along with the elements related to it. This will allow a user to more easily navigate and understand the data being presented.
- When you use an input element, you should always create a relationship between it and a
<label>provides context for what an input actually means to assistive technologies, announcing the label contents each time the input is announced. Not only that, but a proper
<label>increases the clickable area of the input itself, which is useful for users who have trouble clicking on smaller items. There are two ways you can create this relationship:
<!-- Useful when you need the input itself to have an ID -->
<input type='text' id='name' />
<!-- Look, Ma, no ID! -->
<input type='text' />
- Continuing with inputs, you should always use the
typethat makes the most sense for its intended use.
type="text"makes more sense for a name or address field, while
type="tel"would of course make more sense for an e-mail or telephone field, respectively. For certain devices, using the correct
typemay show only the required or additional characters on the keyboard. A
type="tel"input, for example, might make it much easier for users to fill out their phone number by providing larger, numerical-only keys on mobile or tablet devices.
- When you want to present a list of some sort to a user, you should use the appropriate list element (
<dl>) and their related list item elements. This will not only let the user know when they are entering or exiting a list, but also how many items are in the list.
Headings are the
<h6> elements, and like the name implies, these elements act as headings to sections of a page. Landmarks, on the other hand, are HTML elements that act as regions of a page. There are seven native HTML elements that define these landmark regions:
By properly using landmarks and headings, you provide users of assistive technologies a more operable and understandable page: not only can screen reader users navigate a page via landmarks and headings by using navigation keyboard commands (or opening a menu in their screen reader), but these elements also have their roles announced to provide additional context.
If you were to use only
<div> elements to act as these landmarks and headings, maybe adding in some CSS to visually style them, then a screen reader user would have to go through the entire page just to get to a specific section, and they may not be able to actually tell what is a heading or a landmark on the page.
- Read How screen readers navigate data tables to see a great example of just how much context a proper
<table>element provides. There is also a video at the end of the blog post if you want to hear how a table is announced.
- Watch Why headings and landmarks are so important to see how a screen reader interacts with the heading and landmark elements.
This section contains questions for you to check your understanding of this lesson. If you’re having trouble answering the questions below on your own, review the material above to find the answer.
This section contains helpful links to other content. It isn’t required, so consider it supplemental.
- NVAccess provides a download of the NVDA screen reader, one of the more popular (and free!) screen readers available, though it’s only available for the Windows OS. If you’re using a macOS device, you should have the VoiceOver screen reader available to you by default. While the lessons in this section will provide you with what a screen reader will generally announce, it can be invaluable to start using a screen reader yourself to test out your projects and see how they might be perceived.
- Screen Reader Basics: VoiceOver and Screen Reader Basics: NVDA go over some basics for getting started with both brands of screen readers. Both videos are worth watching regardless of which screen reader you choose/is available to you, as they contain some universal information as well.
- Screen reader basics: Orca is a good video to get you started using Orca, the Linux GUI screen reader.
- Screen reader basics: ChromeVox is a starting place for learning to use ChromeVox, the screen reader on ChromeBooks.
- ARIA Landmarks Example lists the native HTML elements that define landmark regions as well as what their role is. If you check this resource out, be sure to enable the button toggles at the top of the page to see how the page is sectioned by landmarks and how it uses headings.