Designing Layouts for Screen Readers
Tags: a11y, frontend, webdev
Published: 2019-02-01 03:33:13

---
title: Designing Layouts for Screen Readers
published: true
tags: accessibility, front-end, webdev
canonical_url: https://benrobertson.io/accessibility/designing-layouts-for-screen-readers
---

It’s easy to think about a layout as being a primarily visual concern. The header goes up top, the sidebar is over here, the call to action is in an overlay on top of the content (just kidding). Grids, borders, spacing and color all portray valuable visual data, but if these hints to the structure of a page are only visible, some users may find your content unintelligible.

You can experience this first hand if you try using a screen reader on the web. When I fired up VoiceOver on my Mac and took it out for a test drive, I realized that to a screen reader user, a lot pages are just a big heap of ‘content’, missing helpful organizational cues.

The experience can be kind of like listening to a long rambling story without any indication to what details are important or related to the main thread of the story. Halfway through the story, you aren’t sure whether it’s worth it to keep listening because you don’t know if you’ll even find what it is you’re looking for. In the context of a website, your screen reader might be halfway through reading you a list of 50 sidebar links when you start wondering if there is any valuable content on the site at all.

Experiences like this are caused by websites that are built with layouts that are only visual. Ideally, however, our visual layouts should point to an underlying organizational model of our content. They should be visual indicators for a conceptual model. The visual indicators are just one way of revealing this model. The Web Accessibility Initiative’s ARIA (Accessible Rich Internet Applications) project provides alternative indicators to users who may need them.

I’ll walk through how to make use of these indicators to make a simple web page easy to use, navigate and read for users of assistive technology. All the example code is available on [github](https://github.com/mergeweb/screen-reader-layout-post).

<small><em>Want to up your accessibility game? Checkout my free email course: <br> ✉️ <a href="/courses/common-accessibility-mistakes/">Common accessibility mistakes and how to avoid them</a>.</em></small>

## Initial Layout

Here’s an example of a page with a pretty simple layout. We’ve got a header at the top containing a logo and navigation, some body content, a sidebar off to the right with a related posts list and a list of social media sharing links, a search box below the content and a footer containing the contact info of our business.

[![Screenshot of the initial layout. Click on the image to preview the page.](https://benrobertson.io/assets/img/designing-layouts-for-sr/initial-layout.png)](https://mergeweb.github.io/screen-reader-layout-post/)

- [Preview the initial layout](https://mergeweb.github.io/screen-reader-layout-post/)
- [View the HTML](https://github.com/mergeweb/screen-reader-layout-post/blob/master/index.html)

Visually, the content is pretty well divided, using a simple grid and background colors to distinguish the different elements. If you fire up VoiceOver on this page, you can navigate through the page pretty well using the next element command. The order of elements in the markup pretty much follows the visual order of elements. First we read the header, then the body copy, then the sidebar, then the search box, then the footer. That’s pretty good. If I press `CAPS + U` to pull up the VoiceOver menus, I can get a list of all the headers on the page and all the links, and navigate directly to them.

![VoiceOver will display a navigable list of all headings on a page.](https://benrobertson.io/assets/img/designing-layouts-for-sr/header-menu.png)

![VoiceOver will also display a navigable list of all links on a page.](https://benrobertson.io/assets/img/designing-layouts-for-sr/link-menu.png)

Just by using well-structured HTML, simple grouping with `<div>` elements and a good use of heading tags we’ve got a decent experience. It’s better than the rambling story websites I mentioned above, but it could be even better.

## Skip Link

- [Preview the skip link layout](https://mergeweb.github.io/screen-reader-layout-post/skip-link.html)
- [View the HTML](https://github.com/mergeweb/screen-reader-layout-post/blob/master/skip-link.html)

First we’ll add a skip-link as the first item of the page. A skip link is a very common accessibility feature that allows users to skip past lengthy lists of links and other information repeated on every web page directly to the main content of the current page.

It’s a link that is the first element in the tab order of the page. It is typically visually hidden, but when focused, it appears on-screen. To visually hide the link, we’ll add the following CSS:

```
.skip {
    clip: rect(1px, 1px, 1px, 1px);
    position: absolute !important;
    height: 1px;
    width: 1px;
    overflow: hidden;
    word-wrap: normal !important; /* Many screen reader and browser combinations announce broken words as they would appear visually. */
}

/* Display the link on focus. */
.skip:focus {
    background-color: #fff;
    border-radius: 3px;
    box-shadow: 0 0 2px 2px rgba(0, 0, 0, 0.6);
    clip: auto !important;
    color: #888;
    display: block;
    font-weight: bold;
    height: auto;
    left: 5px;
    line-height: normal;
    padding: 15px 23px 14px;
    text-decoration: none;
    top: 5px;
    width: auto;
    z-index: 100000;
}

```

The link location of the skip link needs to be an `id` pointing to the main content of the page. In our case, I added `id="main"` to the `<div class="content">` section and gave the skip link a url of `href="#main"`.

If you visit the [skip link page](https://mergeweb.github.io/screen-reader-layout-post/skip-link.html) and hit your Tab key, the link should display. If you fire up VoiceOver and start navigating through the page, the skip link should be the first thing you come across, and clicking it should trigger VoiceOver to start reading the main content of the page.

### WCAG Techniques Used

- [Skip Links](https://www.w3.org/TR/WCAG20-TECHS/G1.html)

With this step, we’ve allowed users to skip straight to the meat of our page, but beyond easily accessing the main content, they still don’t have a good conceptual map of the rest of the page.

## ARIA Roles and Landmarks

One way to provide users with a conceptual map of the page is by using semantic HTML5 elements like `<header>`, `<nav>`, `<main>`, `<section>`, and `<aside>`. These elements have built in data associated with them that is parsed by browsers and screen readers. They create [landmarks](https://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page) on a web page. By using these elements judiciously in place of `<div>` elements, we can provide extra information to assistive technology devices and help the user build a conceptual map of our page.

I’ve maintained the same layout as before, but I’ve swapped some divs for some semantic HTML5 elements. I’ve also added a `role` attribute to the search component. Alternatively, you could keep all the divs and add a `role` instead of swapping them out for the new HTML5 elements. (See [the w3 guidelines for ARIA roles](https://www.w3.org/TR/wai-aria/roles#landmark_roles))

- [Preview the updated layout](https://mergeweb.github.io/screen-reader-layout-post/aria-roles.html)
- 

[View the updated HTML](https://github.com/mergeweb/screen-reader-layout-post/blob/master/aria-roles.html)

- `<div class="header">` becomes `<header class="header">`
- `<div class="main-navigation">` becomes `<nav class="main-navigation">`
- `<div class="content">` becomes `<main class="content">`
- `<div class="sidebar">` becomes `<aside class="sidebar">`
- `<div class="related-posts">` becomes `<section class="related-posts">`
- `<div class="search">` becomes `<div class="search" role="search">`

Now when I fire up VoiceOver and press `CAPS + U`, I get a new Landmarks menu. Inside this menu you can see the following elements:

- banner
- navigation
- main
- complementary
- search
- content information

Selecting any of these menu items takes the user straight to that element, so they can easily navigate through the different elements of a page. If they are at the bottom of the page, they can easily get back to the main navigation in the header via the Landmarks menu.

### WCAG Techniques Used

- [ARIA Landmarks](https://www.w3.org/TR/WCAG20-TECHS/ARIA11.html)

We’ve dramatically increased the navigability of our page and provided an initial map to our users, but we’re missing a few things to make this experience really awesome. First, the names of our site sections are fairly generic. We aren’t exactly sure just from listening to the menu what might be in any of the elements. Second, some elements aren’t easily navigable. For instance, our sidebar components are all grouped under the label ‘complementary’.

We can add some well-thought out ARIA labels to make this experience even better.

## Using Appropriate ARIA Labels

By peppering in some ARIA labels we can give the user an even more detailed conceptual map of our layout.

- [Preview the updated layout](https://mergeweb.github.io/screen-reader-layout-post/aria-labels.html)
- [View the updated HTML](https://github.com/mergeweb/screen-reader-layout-post/blob/master/aria-labels.html)

In this next iteration, I’ve added the following labels:

- `<nav class="main-navigation">` now has an `aria-label` of `Primary Navigation`.
- `<main class="content">` now has an `aria-labelledby` attribute of `main-title` and its `<h1>` has an `id` of `main-title`.
- `<aside class="sidebar">` now has an `aria-labelledby` attribute of `sidebar-title` and its `<h2>` has an `id` of `sidebar-title`.
- Both `<section>` elements in the sidebar now have an appropriate ARIA label.

Let’s fire up VoiceOver again and pull up our Landmark menu with `CAPS+U`. Now we see that the ARIA labels we provided display next to each of our generic menu items. We also have a few extra menu items, because the `<section>` elements we provided labels for (Related Posts, Share Links), now have their own menu items.

![The VoiceOver landmarks menu now shows detailed information about each of the sections on our page, including the aria-labels that we provided.](https://benrobertson.io/assets/img/designing-layouts-for-sr/landmarks-detail.png)

Now an assistive technology user has an equal (and maybe even better) conceptual map of the content and actions they can take on this website compared to a non-assistive technology user. They can get a quick overview of everything on the site, easily navigate to the section of the page they want, and quickly find what they are looking for.

### WCAG Techniques Used

- [Landmarks](https://www.w3.org/TR/WCAG20-TECHS/ARIA11.html)
- [Labelling Landmarks](https://www.w3.org/TR/WCAG20-TECHS/ARIA13.html)

## Wrap Up

With a combination of well-structured HTML markup, thoughtful use of ARIA roles and a careful labeling of site sections using ARIA labels, we’re able to create a user experience for assistive technology users that rivals the experience of non-assistive technology users. We were able to take the conceptual map that was implicit in our visual layout and expose it to assistive technology.

You may find holes in your conceptual map or sections that unnecessarily have the same function. The process can help you clarify your designs, identify areas that might not make sense conceptually or visually, and improve your design for all users of your site.

_Want to dive deeper into building accessible websites? Join my free email course:_ 📨 _[Common accessibility mistakes and how to avoid them](/courses/common-accessibility-mistakes/). 30 days, 10 lessons, 100% fun!_ 😀 [_Sign up here_](/courses/common-accessibility-mistakes/)!