WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: complex table question

for

From: Sailesh Panchang
Date: Oct 29, 2012 10:45AM

I am seeing this as a 4-col table with TH markup which is fine.
JAWS supports multiple rows designated as col headers so it is
possible to use TH with scope=col.
But other screen readers do not. So the 4-col table format is the
safest if one has the option.
Also:
- definition of vesting and portability do not belong inside the table
semantically ... they are not row headers really. Place them outside.
(Done now!)
- Use list markup for data for below age 35 / over age 35 etc. in
cells that have such content.
One does have to use data tables to present descriptive data at times
and that is fine if the content is structured right.
Sailesh Panchang


On 10/29/12, Angela French < <EMAIL REMOVED> > wrote:
> Birkir,
> Thanks. I've made a few changes and look forward to your review. And to
> anyone else's who takes a look.
>
> I took the definitions that were in the Vesting and Portability headers and
> moved them out of the table. I created footnotes from the table to these
> definitions. I also relabeled the column headers to remove the split TRS 3
> column.
> I also added "n/a" to empty cells.
>
> http://sbctc.edu/college/_hr-benefits-connection-SBRP-TRS3NEW.aspx#comparison
>
>
> Angela French
>
>
>>I will take another look at the table tonight and send you impressions, if
>> I
>>come up with something I think may be of use to you.
>>The original answer stands in that I am very happy to see you used the
>> table
>>attributes to mark every single cell with row and column information. It
>> may
>>be a pain in the old behind, but for this type of table it is absolutely a
>>lifesaver.
>>Cheers
>>-B
>>
>>
> > > >