Re: Tables Tutorial - EOWG tweaks

Hi Shawn,

I have just applied the changes, with two changes as outlined below.

On 27 Feb 2015, at 12:31, Shawn Henry wrote:

> [10:16] \* yatil notes that he has updated the table tutorials with 
> the wording of the tables cover page…
>
> Better! - except the first one seems to have been missed (and I think 
> that's the most important one to clarify the image :).
>
> Also, I think tweaking the others as below would help significantly by 
> decreasing the focus on the table categories:
> \* "<h>Tables with two headers</h> Tables with two headers have a 
> simple row header and a simple column header."
> -> <h>Tables with two headers</h> This page covers tables that have a 
> simple row header and a simple column header.
> \* "<h>Tables with irregular headers</h> Tables with irregular headers 
> have header cells that span multiple columns and/or rows."
> -> <h>Tables with irregular headers</h> This page covers tables with 
> header cells that span multiple columns and/or rows.
> \* "<h>Tables with multi-level headers</h> Tables with multi-level 
> headers have multiple header cells associated per data cell."
> -> <h>Tables with multi-level headers</h> This page covers tables that 
> have multi-level header cells associated per data cell.

Here I used the following sentence: “This page covers tables that have 
__multiple__ header cells associated per data cell.”

(We use this wording on the tables concepts page as well.)

> Based on above, the first one would be:
> <h>Tables with one header</h> This page covers tables that have with 
> one header for rows <strong>or</strong> for columns.
> or even more clear:
> <h>Tables with one header</h> This page covers tables that have with 
> one header for rows <strong>or</strong> one header for columns.
> or to better differentiate it from the irregular and multi-level:
> <h>Tables with one header</h> This page covers tables that have one 
> simple header for rows <strong>or</strong> one simple header for 
> columns.
>
> (I prefer the 2nd or 3rd option!)

I have used the third option and changed the following sentence to flow 
better, see:
https://github.com/w3c/wai-tutorials/commit/f47bb3414f43fbcce874eb4c6db47c74e3f4398e

Cheers,
Eric

>
> ~Shawn




--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at Wold Wide Web Consortium (W3C)