RE: SCOPE element

Thanks John

 

Thanks for the correction about SCOPE, up its an attribute for TH and TR.
Sorry.

 

I think colgroup and colspan are two different things. Colgroup is an
element colspan is an attribute.

 

Table cells can span across more than one column or row. The attributes
COLSPAN ("how many across") and ROWSPAN ("how many down") indicate how many
columns or rows a cell should take up.

 

COLGROUP is an element that defines groups of table columns. With this
element, you can group columns for formatting. This element is only valid
inside the <table> tag. But it’s purpose is not really to be used with the
SCOPE.

 

JAWS 7.1 and 9 might support COLGROUP but are you sure they support COLSPAN.
I ask you about that because Shailesh said COLSPAN is not supported.

 

Like I say. This is a hairy and confusing beast.

 

Cheers

David MacDonald

 

 

access empowers people...

        ...barriers disable them...

 

HYPERLINK "http://www.eramp.com"www.eramp.com

From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of Slatin, John M
Sent: Monday, March 12, 2007 5:55 PM
To: David MacDonald; public-wcag-teamc@w3.org
Subject: RE: SCOPE element

 

David, thanks so much for this rewrite (and the backstage work hat went into
it). 

 

A couple of notes:

 

1. scope is an attribute, not an element. It is defined for both <th> and
<td> elements, as well as <rowgroup> and <colgroup>. The scope attribute can
have a value.  of "wor" or "col" (e.g., schoe="row" or scope="col").

2. <rowgroup> and <colgroup> are elements; they're not the same as the
*attributes* rowspan and colspan (which have integer values, e.g.,
rowspan=3")

3. JAWS 7.10 introduced support for <rowgroup> and <colgroup> elements (it's
much better in JAWS 8.0)

4. JAWS 8.0 supports the scope attribute in complex tables, including its
use with <rowgroup> and <colgroup>; at least one bug has been identified,
but a patch has been released since then and I don't know whether the bug
has been repaired or not.

 

I hope this helps.

 

John

"Good design is accessible design." 

Dr. John M. Slatin, Director
Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, fax 512-495-4524
email john_slatin@austin.utexas.edu
Web HYPERLINK
"http://www.ital.utexas.edu/"http://www.utexas.edu/research/accessibility 

-----Original Message-----
From: public-wcag-teamc-request@w3.org
[mailto:public-wcag-teamc-request@w3.org] On Behalf Of David MacDonald
Sent: Monday, March 12, 2007 2:28 PM
To: public-wcag-teamc@w3.org
Subject: SCOPE element

I had an action to revise H63 on the SCOPE element. It was a killer but I
think its good now.  It is here:

 

HYPERLINK
"http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_individual.php?id=1
078"http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_individual.php?i
d=1078

 

or:

 

HYPERLINK "http://tinyurl.com/26m25j"http://tinyurl.com/26m25j

 

 

David MacDonald

access empowers people...

        ...barriers disable them...

 

HYPERLINK "http://www.eramp.com"www.eramp.com

 

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.9/719 - Release Date: 3/12/2007
8:41 AM

 

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.9/719 - Release Date: 3/12/2007
8:41 AM


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.9/719 - Release Date: 3/12/2007
8:41 AM