WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Steve Faulkner
Date: Sep 22, 2011 9:51AM

thanks Sailesh, thats good to know.

On 22 September 2011 16:41, Sailesh Panchang < <EMAIL REMOVED> >wrote:

> >I don't know of any AT that take notice of the [thead] [tfoot] [tbody]
> Window-Eyes does. It announces when one crosses over from thead into
> tbody and into tfoot.
> Sailesh
>
> On 9/22/11, Steve Faulkner < <EMAIL REMOVED> > wrote:
> > hi vincent,
> >
> > [thead] [tfoot] [tbody] elements are not included in the accessble tree
> > exposed to AT. (and example of what is exposed by Firefox can be seen
> using
> > the DOM inspector > accessible tree feature.
> >
> > I don't know of any AT that take notice of the [thead] [tfoot] [tbody]
> > elements.
> >
> > I would suggest that the only thing that affects table reading order is
> the
> > order of rows and cells in the code.
> >
> > regards
> > Stevef
> >
> > On 21 September 2011 19:23, Vincent Young < <EMAIL REMOVED> > wrote:
> >
> >> 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
> >>