W3C home > Mailing lists > Public > public-html-a11y@w3.org > May 2013

resolving open longdesc bugs - new proposals

From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Wed, 01 May 2013 12:38:39 +0300
To: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-ID: <op.wweiipvcy3oazb@chaals.local>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21565 longdesc on  
presentational images
propose to resolve invalid, as it isn't an issue on longdesc but on ARIA  
and maybe WCAG techniques

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21781 affect of base /  
xml:base
Leaning to adding a statement reminding developers that this needs to be  
taken into account, but waiting on further info

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21778 user agents MUST  
present longdesc.
propose to make the requirement apply to valid longdesc values only,  
leaving the invalid case unspecified for now as there are different  
strategies that can be applied for different kinds of invalid content and  
I don't think we yet have enough experience to insist on conformance  
requirements for the error cases.
This bug depends on https://www.w3.org/Bugs/Public/show_bug.cgi?id=21564  
allow user agents to decide what to do with invalid longdesc, and blocks  
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21778 define behaviour for  
empty values, both of which would also be resolved by this approach, as  
fixed and wontfix respectively.

cheers

Chaals

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Wednesday, 1 May 2013 10:39:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:33 UTC