WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Examples of and justification for id/headers incomplex tables

for

From: Spellman, Jeanne
Date: May 24, 2007 12:30PM

> Because scope is simpler, shorter and less error-prone than
id/headers,
> it would great if worked for complex tables and had better support.
It
> would be great also if all complex tables could be transformed into
> simple tables. I agree, they are a big pain to mark up.

Scope only seems simple in theory. When working with complex, dynamic
tables, id/header is easier, as they are simple attributes that are
easily expressed as variables. Setting up colgroups and the varieties of
row group elements are problematic in CSS styling and cross-browser
implementation flaws. For financial institutions that live and breathe
complex data tables, the id/header attribute is a simple solution that
is reliable cross-browser.

Scope does not address the problem of tables with merged cells. Only
id/header allows the developer to precisely assign the header for a
merged cell cross-browser.

Laura, I haven't forgotten about getting you specific examples, but I'm
seeking permission to post code examples.