[Bug 21987] Consider adding a sister attribute to act as a toggle to trigger longdesc discoverability.

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

--- Comment #5 from Laura Carlson <laura.lee.carlson@gmail.com> ---

Hi Chaals,

(In reply to comment #4)
>>> (In reply to comment #3)
>> (In reply to comment #2)
>> > even so, script is not within the realms of everyone.
>> 
>> This is true. Not all authors know JavaScript or CSS. I don't see why the
>> browser couldn't provide an easy way to do this, for authors of limited
>> skill sets.

> The browser could.

Yes. I believe that getting it implemented is what Chris had in mind.
Specifying a new attribute would allow browsers to enable a *super simple*  way
for *authors* to explicitly trigger longdesc discoverability on individual
images. It would provide author control of design in a granular manner.

> The simplest way to do that, of course, is an extension.

Do you mean a browser extension or an authoring tool extension? 

As you already know and as previously noted we already have various browser
extensions that enable direct user discoverability in browsers  [1]. 

Does your code do anything different than provide direct user discoverability? 

Does it allow authors or authoring tools to simply add a sister attribute
(whatever it be named) into their markup in a conforming way that will make
longdesc discoverable? Again, the idea of the sister attribute is to allow
authors to easily surface discoverability in browsers by adding a simple sister
attribute. Then if that sister attribute was present, browsers would do
something: add the link or a border or an icon or whatever in whatever way was
agreed upon for that particular device.

Thanks.

[1] http://www.d.umn.edu/~lcarlson/research/ld-ua.html

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

Received on Monday, 13 May 2013 11:34:36 UTC