WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Table Header/Footer/Body Placement and Reading Order

for

From: Vincent Young
Date: Sep 21, 2011 6:51PM


Thank you for the input Angela. As of right now, I'm going to write this
off as a non issue. The following code order: thead/tfoot/tbody poses no
usability issues for all users.

On Wed, Sep 21, 2011 at 12:06 PM, Angela French < <EMAIL REMOVED> > wrote:

> As a sighted person, when I see a footer on a table, I read it before I
> look at the table data and I ask "why aren't 'footers' put at the top?" :-)
>
> >-----Original Message-----
> >From: <EMAIL REMOVED> [mailto:webaim-forum-
> > <EMAIL REMOVED> ] On Behalf Of Vincent Young
> >Sent: Wednesday, September 21, 2011 11:24 AM
> >To: WebAIM Discussion List
> >Subject: [WebAIM] Table Header/Footer/Body Placement and Reading Order
> >
> >So the HTML specification says construct tables in the following order:
> >
> >[thead] [tfoot] [tbody]
> >
> >I've user tested tables, but none when tfoot was involved. Assistive
> >tecnology tends to read tfoot before any tbody information. Does this
> cause
> >any usability issues? I've not seen this really discussed anywhere such
> as on
> >WebAim's accessible tables article. I tend to use thead/tfoot/tbody for
> >semantic purposes, I guess. It's also really easy to style each
> >differently through CSS with these elements in place.
> >Thoughts/opinions/whatevers?
> >
> >
> >
> >
> >--
> >WebHipster Interactive, ltd.
> >Vincent Young - Principal
> >33 E. Lincoln St.
> >Columbus, OH 43215
> >p: 614.607.3400
> >f: 339-674-3400
> >e: <EMAIL REMOVED>
> >w: http://www.webhipster.com
> >