WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible table where some data spans multiple columns

for

From: Jeremy Echols
Date: Nov 13, 2018 3:37PM

No worries, I understood what you meant.

We ended up just duplicating the data so all rows and columns have exactly one cell. Trying to ensure manual header match-up seemed error-prone and easy to break without noticing (the table is on a drupal site, which just makes it that much more fun).

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Tuesday, November 13, 2018 8:22 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Accessible table where some data spans multiple columns

Just to be clear, having a row header or column header span multiple cells
(eg, <th scope="row" rowspan=3>) works very well, but that's because all
the data cells are individual cells. You just have multi-level headers.

What doesn't work as well is having single row headers or column headers
(ie, no spans) but having a data cell span several cells. That's the
scenario you have and is fixed by using the ID and HEADER attributes.


On Tue, Nov 13, 2018 at 8:26 AM Jeremy Echols < <EMAIL REMOVED> > wrote:

> Interesting. I knew about associating multiple headers, but didn't know
> that was necessary just for colspans. I also didn't really see the table
> as being confusing, but now that you point that out, it does indeed seem a
> little difficult to navigate.
>
>