[Bug 24679] Addition and improvements to the table over (non-)layout table heuristics

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24679

--- Comment #8 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to steve faulkner from comment #7)

> If something is not implemented I don't see why it should be added as a
> suggested heuristic, 

Is it mportant to spare AT vendors from thinking about the heuristic effect of
@sortable until it has browsers support it and authors use it?

If the answer is yes, then your approach makes sense.

However, I disagree that that is a good approach beacause I think the spec, for
new features, should describe the situation we want to end up with. As
implementation takes place - or not - the spec should modify what it says, to
match actual implementations, including remove @sortable - from the list of
content attributes and from the tabe over layout table heuristics.

I suppose the vendors that make use of the heuristics are also aware of the
implementation status They might choose to postpone the heuristics until their
AT supports @sortable anyway. But I don’t see why this should make us not
describe the intended - or most likely - heuristic effect.

For other, new features, the default accesibility related features (such as
ARIA features) are added in tandem with the very feature itself. E.g. you did
not poostpone defining the default @role value for the element <main> until
there was evidence that authors used it and browsers had implemented it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 16 February 2014 21:40:54 UTC