This blog on the impact of inaccessible tables is a continuation of our series, looking into what comparisons can be made between inaccessible elements on websites, which was inspired by an AXSChat Podcast

After finishing my original blog, I decided to expand and tell you a bit more about specific areas of assistive technology features that should be used and accessible within a digital platform. This should be the case whether on a website, a document, or any other digital information.

In this specific blog, we discuss the impact that inaccessible tables have on websites and in documentation.

The Problem With Unformatted Tables in Documents

Incorrectly formatted tables in a document make the content incredibly challenging for a screen reader user to understand.

When people navigate to a cell on a table, which is not formatted correctly, the information within it is not identifiable. For example, the screen reader may just read out a number like ‘45’. If no other information is provided from the heading or row titles, it makes it very difficult for the user to get any context. The benefit of formatting headings and rows is the screen reader user will be able to hear both the heading and row titles, which in turn, makes the content of the cell informative. 

Comparisons Between Accessible and Inaccessible Tables And The Context They Provide

An Example of An Inaccessible Table With No Headings Present

Imagine that you are looking up times on a bus timetable. However, there are no column or row headings labelled. 

For example:

09:2010:2011:2013:4014:5017:45
10:2511:2513:4514:5517:50
09:2510:2711:2713:4714:5717:52
09:2810:3011:3013:5015:0017:55
09:3010:3211:3213:5215:0217:57
09:3210:3411:3413:5415:0417:59
09:3310:3511:3513:5515:0518:00

You would not know what 11:32 would be indicating.

How Headings Can Give Meaning To Users 

Now, what about this table? It’s providing the same information to users, however with the headings being formatted, they can now tell that the time of 11:32 will be their arrival time:

Arrival TimeArrival TimeArrival TimeArrival TimeArrival TimeArrival Time
09:2010:2011:2013:4014:5017:45
10:2511:2513:4514:5517:50
09:2510:2711:2713:4714:5717:52
09:2810:3011:3013:5015:0017:55
09:3010:3211:3213:5215:0217:57
09:3210:3411:3413:5415:0417:59
09:3310:3511:3513:5515:0518:00

There is a little bit of an improvement to the information being shown previously, but you still don’t know where the bus is actually stopping. 

This table is better, isn’t it, as you now have the information you would need for your journey:

Swansea City Bus Station To Cwmdonkin Drive
Arrival TimeArrival TimeArrival TimeArrival TimeArrival TimeArrival Time
Swansea City Bus Station09:2010:2011:2013:4014:5017:45
Uplands, Eaton Crescent10:2511:2513:4514:5517:50
Uplands, Post Office09:2510:2711:2713:4714:5717:52
Glanmor Park Road09:2810:3011:3013:5015:0017:55
Penlan Crescent, Notts Gardens09:3010:3211:3213:5215:0217:57
Richmond Court09:3210:3411:3413:5415:0417:59
Cwmdonkin Drive09:3310:3511:3513:5515:0518:00

How Blank Table Cells Can Cause Confusion For Users

When it comes to a table’s content, all cells need to have something within them. The reason for this is when a screen reader user navigates to a cell which is blank, they don’t know if it is meant to be blank or whether there should be something in there which may be inaccessible for assistive technology, meaning it cannot be read out. 

For example, take a closer look at the table above, and you will see there is a blank cell. Does this mean that the bus does not stop at Uplands Eaton Crescent on the first run? That is the presumption, so this is not just an issue for someone who uses a screen reader but for everyone. By putting in something like ‘no stop’, will assist all users (that is if this is the case).

A Useful Function in Microsoft Excel That Could Improve All Inaccessible Tables

A bigger example of the need to format headings and rows correctly can be found with spreadsheets.

It is funny really, as spreadsheets have a key function that could help all users. When there is a lot of data within a spreadsheet, there is a feature that allows the headings and the first column row to move with the information that you are looking at. By freezing the rows and columns in this way, you don’t lose the information, no matter where you are within the spreadsheet.

If we all adopted these features, not only for people that don’t need assistive technology but for everyone, then the person on a website or someone reading a table in a document would have a more positive experience.

Eliminating Inaccessible Digital Platforms

I know I have used this last paragraph at the end of each of this series of blogs, but it relays the important message of all the blogs written:

These are just a few comparisons between most people’s everyday life experiences to one of the inaccessible features of digital information in their life. However, there really is no need for any inaccessible areas, as there are always alternatives. 

Think about when you could not get access to something. Whether it is in a shop or around your normal life experiences. There is no real reason why you should not be able to gain access. It is usually due to someone having made it inaccessible to you because of the design and not thinking of your individual needs as a customer in a specific situation.

It’s time to make a change and be inclusive.

Over the next few months, I’ll be blogging about ways that you can adapt your websites to achieve digital accessibility and improve the user experience for everyone.

For more details about how we can help with website accessibility testing, please get in touch with our team today.