RE: 48-Hour Consensus Call: InstateLongdesc CP Update

Charles McCathie Nevile wrote:
> 
> TL;DR: I think the explanation should be improved, but I can live with
> it.
> I don't see a viable alternative to longdesc after more than half a
> decade
> of many smart people trying, so I conclude we aren't ready to replace
> it.

<snip>
> 
> I conclude that while implementation uptake has been very slow, it
> exists
> and shows that longdesc implementation is feasible and meets the
> requirements. Therefore dropping longdesc in the absence of a workable
> alternative is at best premature and probably harmful, and at worst an
> unequivocal step backwards for accessibility.

+1

I support this Change Proposal

JF

Received on Monday, 17 September 2012 02:00:28 UTC