W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2018

RE: accessible tables

From: Jeremy Echols <jechols@uoregon.edu>
Date: Mon, 7 May 2018 15:46:25 +0000
To: WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <31ec17420a8a4ce4823f8abd56a0a73a@ad-oh-ex01.ad.uoregon.edu>
I feel like this would make sense as simply two tables.  Having a single table, this seems a bit weird, but if it were clearly two distinct tables, I think that it would make more sense.  The HTML would flow from "Thin/100" to "ExtraLight/200" properly, rather than flowing from "Thin/100" to "SemiBold/600".

As a sighted user, the table is manageable, but it took my brain a second to treat the table as if it had two separate columns of key/value pairs.  Having two clearly separated tables makes it work better for me and immediately deals with the reading order you want.

-----Original Message-----
From: Michael A. Peters <mpeters@domblogger.net> 
Sent: Friday, May 04, 2018 1:21 PM
To: WAI Interest Group <w3c-wai-ig@w3.org>
Subject: accessible tables


I am sure this is covered somewhere, but I just can not find where.

Tabular data, 9 pairs of key = value data. But the table cell contents are short, so instead of just two columns I want to do four columns where the third is a continuation of the first and the fourth is a continuation of the third, e.g.

[ caption of the table]
[ key ] [ value ] [ key ] [ value ]
001     first     006     sixth
002     second    007     seventh
003     third     008     eighth
004     fourth    009     tenth
005     fifth

Is there a way to mark that up so screen readers will read them as pairs in the order 001 to 009 in order?

I can't be the first to have needed this.

Received on Monday, 7 May 2018 15:46:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:17 UTC