Tables

The What

Tables are objects that help us format content. It can be tempting to use tables to create a specific page layout, but this actually makes it harder for screen reader users (and sometimes, sighted users) to find and parse information. Really, tables should only be used to communicate data. Rubrics are a common example of tables we might use in teaching. Tables are also commonly used to display information like health insurance plan comparisons (e.g. cost per service for a PPO vs. HDHP).

The How

Level 1: Making a Start

First, ensure that you’re only using tables to communicate data. More specifically, tables should be used to communicate relevant relationships among data. For instance, if you’re offering students a variety of topics for their final paper, you probably want to use a list. If, instead, you’re presenting the temperature at which each of a select variety of substances glows, a table may be a good choice (esp. if you have few enough data that you don’t need an entire spreadsheet).

When creating tables, ensure that there is at least a header row, if not both a header row and column. A header row provides labels for each column of data. A header column provides labels for each row of data.

Finally, avoid using tables in platforms where you aren’t able to make them accessible. Currently, Gmail and Moodle lack native features for adding the structure that makes tables accessible. Google Docs has a “pin header row” feature, but this doesn’t add the necessary structure to have a screen reader treat the header row as a header row. It may help sighted readers, but it isn’t accessible to others. If you have to use a table in these platforms, create your table elsewhere, ensure that it’s accessible, and export/import or copy/paste into your chosen platform. In many cases, the structure will transfer.

Use the links below to learn how to create tables and add header rows/columns.

Level 2: Refining Your Approach

Let’s kick things up a notch. You’ve created your basic table—great! A few more considerations are in order.

First, you want to avoid merging cells. This can wreak all kinds of havoc for screen readers. It’s just not nice to do to someone who’s using a screen reader to navigate your table.

Second, create a title for your table. This title may be visible or invisible depending on the software you’re using. Either way, screen readers will still see it and announce the table in a more detailed way. If you have the option, it’s also a good idea to add a caption and/or alt text to your table. This allows screen reader users to preview the information before hopping into the table, which can save them time and frustration (tables aren’t super easy to navigate, even for folks who use screen readers a lot). A caption that remains visible also helps sighted readers better understand what a table is trying to communicate—a win-win!