Re: Description link consensus

Hi Leif,

>> The question I would ask HTML5 Accessibility Task Force members is if
>> they agree to lose the opportunity to provide a native HTML5 long
>> description feature for other elements besides <img> and agree to
>> shirk off that responsibility to a future version of
>
> May be we should put off that question too, until after your CP has
> been evaluated?

If you mean the HTML Working Group decision survey for ISSUE-30
"Should we include longdesc in HTML5", I agree.

> I have now withdrawn my own such extension proposal.

The deadline for Issue 30 counter proposals was last June so your CP
had no bearing on Issue 30 (unless it was agreed to add your verbiage
to my proposal, which didn't happen).

> Or you could promise yourself or whoever to do take it up - despite
> what Sam has said to that idea - but nevertheless move on, for now.

My question to Sam to consider the two step process has not been
answered yet. What he will say is beyond my control. So  Leif, I have
no choice but to move on for now.

>> If no use
>> cases exist maybe we have it covered and I worry for nothing.
>
> At least in a general sense, use cases exist - it seems to me the A11Y
> TF agree on that.

General use cases have not helped any of the accessibility task force
change proposals prevail. I think that use cases need to be specific
to have any impact on the HTML Chairs decisions.

Best Regards,
Laura

-- 
Laura L. Carlson

Received on Monday, 26 March 2012 17:10:04 UTC