Re: table headers - clear description of problem

You are dodging the point Ian,
the spec in this instance has not followed the process outlined.

Currently the spec contains a feature that is not implemented by any
UAs, thus the spec does not provide a practical viable method for
marking up complex irregular data tables accessibly.

There is a feature that is well support by UAs and is used to ensure
that accessibility of complex irregular data tables, but you refuse to
add it.

There is no reason, other than your arrogance and autocratic control
over the contents of the spec, to not include a practical, supported
and used feature to the spec.

If in the future, before the ten years of HTML5 development are over,
the new features become well supported by AT's, then  by all means
remove the supported but more cumbersome id/headers feature from the
spec.

--stevef

2008/8/26 Ian Hickson <ian@hixie.ch>:
> On Tue, 26 Aug 2008, Laura Carlson wrote:
>>
>> Anyway, has the new replacement for table headers/id gotten to step
>> number two in your process? Have AT implementers committed to
>> implementing your replacement for headers/id? If so which ones?
>
> It has unfortunately been nigh on impossible to get any kind of consistent
> participation from AT vendors. If anyone can help with this, please let me
> know.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>



-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html

Received on Tuesday, 26 August 2008 07:45:54 UTC