WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Table Headers In Separate Table From Data

for

From: Mallory
Date: May 3, 2018 1:51AM

When I've done the two-tables thing, IF I don't need the headers clickable for sorting or select-column or whatnot, then I make the visible table-with-only headers the aria-hidden one. Screen reader users then at least get 1 full single table, and the headers on it are simply covered up by the aria-hidden table showing headers.

Where I have trouble is when I need click events and key listeners on those headers.

cheers,
_mallory

On Wed, May 2, 2018, at 8:04 PM, Sailesh Panchang wrote:
> Here is a solution that seems to work quite alright and I have pointed
> developers to this in the past:
> http://juicystudio.com/article/accessible_data_tables_static_headers.php
> Thanks,
> --
> Sailesh Panchang
> Principal Accessibility Consultant
> Deque Systems Inc
> Phone 703-225-0380 ext 105
> Mobile: 571-344-1765
>
>
> On 5/2/18, Jonathan Cohn < <EMAIL REMOVED> > wrote:
> > Yes, we have several of these tables on our administration site, and are
> > currently working on making them appear as one table. Unfortunately it isn't
> > only the fact that the two tables need to be pseudo-merged, we also have a
> > checkbox to select the row and a button to edit data on a row in the first
> > column, and need to make sure items are labeled appropriately. Our plan
> > right now is to have the table with only headers be marked with aria-hidden,
> > and then to have the second table have column headers that are being masked
> > visually by the first table but that will be available to the screen reader.
> >
> > I have also fooled around with using aria-owns and role=presentation, but
> > have had not been able to consistently have this provide a good rendering in
> > all systems.
> >
> > Jonathan Cohn
> >> On May 2, 2018, at 1:00 PM, Jonathan Avila < <EMAIL REMOVED> >
> >> wrote:
> >>
> >>> I am curious if list subscribers have an idea why web developers use a
> >>> design that puts the column headers of a table in a separate table. What
> >>> benefits does this achieve, independent of accessibility concerns, that
> >>> have caused this to start happening?
> >>
> >> People do this so that the table body can scroll and the header can be
> >> fixed.
> >>
> >> Jonathan
> >>
> >> Jonathan Avila
> >> Chief Accessibility Officer
> >> Level Access
> >> <EMAIL REMOVED>
> >> 703.637.8957 office
> >>
> >> Visit us online:
> >> Website | Twitter | Facebook | LinkedIn | Blog
> >>
> >> Looking to boost your accessibility knowledge? Check out our free
> >> webinars!
> >>
> >> The information contained in this transmission may be attorney privileged
> >> and/or confidential information intended for the use of the individual or
> >> entity named above. If the reader of this message is not the intended
> >> recipient, you are hereby notified that any use, dissemination,
> >> distribution or copying of this communication is strictly prohibited.
> >>
> >>
> >> -----Original Message-----
> >> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> >> Of KellyFord
> >> Sent: Wednesday, May 02, 2018 12:47 PM
> >> To: 'WebAIM Discussion List'
> >> Subject: [WebAIM] Table Headers In Separate Table From Data
> >>
> >> Hi,
> >>
> >>
> >>
> >> Although it doesn't happen too often, over the past couple years I have
> >> noticed an increase in web experiences where table column headers are put
> >> in
> >> a separate table from the data. One of the financial sites I use, that
> >> used
> >> to be a go to for easily demonstrating how proper table headers make
> >> reading
> >> tabular data easy with a screen reader, has now incorporated this sort of
> >> design.
> >>
> >>
> >>
> >> I am curious if list subscribers have an idea why web developers use a
> >> design that puts the column headers of a table in a separate table. What
> >> benefits does this achieve, independent of accessibility concerns, that
> >> have
> >> caused this to start happening?
> >>
> >>
> >>
> >> Again this is not entirely recent but several years ago I'd say I never
> >> encountered this. Now the times I encounter it is certainly greater than
> >> 0.
> >>
> >>
> >>
> >> Kelly
> >>
> >> > >> > >> > >> > >> > >> > >> > >> > >
> > > > > > > > > >
> > > >