[Bug 21678] i18n-ISSUE-251: Invalid content in longdesc

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

Charles McCathieNevile <chaals@yandex-team.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Charles McCathieNevile <chaals@yandex-team.ru> ---
There is a tension between useful repairs and long-term encouragement.

I am working on a browser extension that identifies non URLs and converts them
to data URLs, because this will provide users with access to descriptions that
might be useful. I believe this will lead to a significant improvement in
accessibility for actual users, although I understand the principle that I am
thereby solving a problem in a way that may lead authors to stop worrying about
fixing it.

Based on the heriarchy of needs principle, I believe the correct solution is
still to allow user agents to make this repair,  Validators SHOULD report when
the attribute is incorrect (and accessibility testing should obviously include
this simple validation as well as more).

On the other hand, I think an implicit use case and requirement (i.e. they have
somehow not been put into the spec) is to provide support for localisation of
descriptions. Using HTML content (whether in the page or externally) can
achieve this, and I think it should be explicitly noted. I'd welcome
suggestions on this (you may want to raise a new bug).

I also invite you to review the editor's draft, which has been updated.

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

Received on Friday, 12 April 2013 17:04:24 UTC