WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Tables with collapsible rows

for

Number of posts in this thread: 3 (In chronological order)

From: Emily Ogle
Date: Mon, Jul 09 2018 3:14PM
Subject: Tables with collapsible rows
No previous message | Next message →

How would Tab order work if we have a table with collapsible rows? The row headings have rows within that can be collapsed or expanded.

Should we make it so you tab to the table and arrow everything within it, including the rows that can be expanded/collapsed? Tabbing again would take you back out of the table. Or should these expandable rows be treated as part of the tab order?

From: glen walker
Date: Mon, Jul 09 2018 3:29PM
Subject: Re: Tables with collapsible rows
← Previous message | Next message →

Tough call without further info. Is the table like a grid/spreadsheet
where arrowing through the cells would be expected behavior?

If the table is static, just data, but some rows can be expanded, I might
expect each expandable element to be a tab stop. But then, the table might
be considered a composite object, like a tree, where a tree as a whole is
just one tab stop and not each expandable branch, so that might be
appropriate for your case too.

So I can see all three behaviors depending on further info.


On Mon, Jul 9, 2018 at 3:14 PM, Emily Ogle via WebAIM-Forum <
= EMAIL ADDRESS REMOVED = > wrote:

> How would Tab order work if we have a table with collapsible rows? The row
> headings have rows within that can be collapsed or expanded.
>
> Should we make it so you tab to the table and arrow everything within it,
> including the rows that can be expanded/collapsed? Tabbing again would take
> you back out of the table. Or should these expandable rows be treated as
> part of the tab order?
>
>
> > > > >

From: Emily Ogle
Date: Tue, Jul 10 2018 8:03AM
Subject: Re: Tables with collapsible rows
← Previous message | No next message

Thanks. This table is indeed functioning as Excel would, so I'll advise the heading rows be treated as cells and not part of the tab order.

> On Jul 9, 2018, at 4:29 PM, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>
> Tough call without further info. Is the table like a grid/spreadsheet
> where arrowing through the cells would be expected behavior?
>
> If the table is static, just data, but some rows can be expanded, I might
> expect each expandable element to be a tab stop. But then, the table might
> be considered a composite object, like a tree, where a tree as a whole is
> just one tab stop and not each expandable branch, so that might be
> appropriate for your case too.
>
> So I can see all three behaviors depending on further info.
>
>
> On Mon, Jul 9, 2018 at 3:14 PM, Emily Ogle via WebAIM-Forum <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> How would Tab order work if we have a table with collapsible rows? The row
>> headings have rows within that can be collapsed or expanded.
>>
>> Should we make it so you tab to the table and arrow everything within it,
>> including the rows that can be expanded/collapsed? Tabbing again would take
>> you back out of the table. Or should these expandable rows be treated as
>> part of the tab order?
>>
>>
>> >> >> >> >>
> > > >