Make it Accessible: Better Layout with HTML
Make it Accessible: Better layouts with HTML
In this article, I'm going to teach you how to use the HTML tags , and , and how they can improve your web applications accessibility.
Here you can access all the resources used in the article.
The Problem
Web applications are built with HTML, and even though it isn't a programming language, it is nontheless complex. One of the first issues you may encounter is knowing which element to use, and the huge amount of elements available makes this issue even more challenging.
When it comes to your page's layout, some of the options are; , and . Today, you're going to learn when you should use each of them.
The Solution
First, we will conceptualize each of the elements I just mentioned. You can learn more about these in the w3c wai aria practices guide, but let's discuss those concepts here:
> The element is often used as a container for other HTML elements to style them with CSS or to perform certain tasks with JavaScript.
> w3schools.com
You may be tempted to use with some styles instead of learning about the available elements in HTML5. I have to tell you, if you do that, you're hurting your users. Each element has a specific purpose, and you should be using the right element. is useful when you want to group some elements and give them some styling, that doesn't mean you should make everything with .
> The tag defines sections in a document, such as chapters, headers, footers, or any other sections of the document.
> w3school.com
This is a very important tag as you start your accessibility journey. It gives context to your users, specially those with Screen Readers. By "context", I mean that if you wrap a group of elements with a section and give it an accessible name, once users focus one of the elements, it reads the parent container too.
> The tag specifies independent, self-contained content.
> w3school.com
Almost every application has some kind of catalogue showing several items having the same styles, and if you think it through, these items could be placed anywhere without any context. Articles are cool for those cases, even though these aren't landmarks, it's common for Screen Readers to have a mechanism to allow users to navigate through articles easily.
The Implementation
Next, we're going to do a small sample using each of the mentioned elements. Let's start with the .
Using divs right
Now that you are fully aware of the purpose of a , it is time to use it. For this one, I decided to take the easy road and make a very simple example. Let's say you have multiple "things" you want to group, and to which you want to apply some additional styling. That can be easily done like this:
`
To test this, create a file with the .html extension containing what I just gave you, and open it with your preferred browser. You'll notice that the first two have a light gray background. Once again, very simple and easy to follow. Let's jump to the next example.
Sections are the way to go
For this one, I was looking for a more exciting example. Let's say you are building an application for a movie theater that allows customers to order tickets online. If you buy a ticket, you want to have a page where you can see all the details about the movie and your ticket.
Let's start by thinking it through. We want to see all the information about the movie, title, synopsis, a banner image, and a genre. When it comes to the ticket, I want to see its worth, my seat number, and the time left for the show to start.
The HTML for something like this would look like this:
`
For now you can ignore the styles, it's just to make it look less ugly, what I want you to pay attention to is the HTML part. Look at how I created two sections- one for the movie details, and one for the ticket summary. Another important takeaway is how I used aria-label and aria-labelledby. Both have the same results, but in the movie details, I wanted to read "Movie Details" instead of the movie title, and in the case of the Ticket Summary, it's different because we want to read the same title.
By structuring your HTML document this way, using sections with the proper accessible names, you're not only giving context to the user, but you're creating a hierachical view of the landmarks of your application. This makes it easier for Screen Readers to understand your page, and as a consequence, you get better usability for your disabled users.
Articles are useful too
I know that example may have set the bar a little high. For this example, I'm doing something simpler. Let's say that this movie theater we are "working for" wants to show all the available movies to possible customers. This is where articles shine the most, because let's face it, no matter how many movies there are, all of them will have the same styles.
Let's roll up our sleeves, and create a new html file with this content:
`
Remember to focus on the HTML structure, not the styles. The first time I saw this kind of code, I was like, *wow, what's all that aria stuff doing?* Today, I'm going to make this easier for you.
> First of all, I have to remind you that all of these ideas come from the WAI ARIA Authoring Practice Guide.
One thing to notice before heading to the code is that a list of movies is a feed. Also, don't reinvent the wheel. The WAI ARIA guide has a very detailed description of how a feed should be implemented while prioritizing accessibility. You have to start with and role="feed", next you have to work on the articles.
Setting up the feed container is very simple. What's not so straightforward are the articles themselves. Each of the aria properties has a specific purpose:
- aria-labelledby: Title of the movie.
- aria-describedby: Additional information about the movie.
- aria-posinset: Position of the movie in the list.
- aria-setsize: Size of the list of movies.
There's also a tabindex="0" because once in a feed, screen readers provide users with additional navigation mechanisms that require us to make the articles "focusable".
NOTE: All the in the samples have an empty alt like this alt="". It's because using an empty alt tells screen readers to ignore the images entirely, in a real life project for images that provide information, you always give a proper alt value.
Conclusion
Every time I write one of these series, I come up with the same conclusion: Just use HTML! I'm even thinking of changing the name to "It's Already Accessible". It's common to hear developers saying that HTML is too simple. It might be for some, but you still have to learn it. Whenever you write an application, try to build it following patterns like the ones in WAI-ARIA. Make sure to follow their specifications, and you'll make applications all of your users will love....
