Hi all,
On Wed, 27 Mar 2013 16:46:05 +0100, Laura Carlson
<
laura.le...@gmail.com> wrote:
> On Wed, Mar 27, 2013 at 10:11 AM, Dominic Mazzoni
>> Yes, this is a great list to discuss longdesc in Chrome. Now that the
>> spec has been published I think we can add it.
>
> That's terrific. Thank you very much.
Yes, I would love to see this. (It would be the easiest way for me to get
support into Yandex' browser :) ).
>> Adding support to longdesc for assistive technology should be
>> straightforward, especially on Windows where some screen readers already
>> support it. I filed:
http://crbug.com/224287
>>
>> Making longdesc available to all users through the regular user
>> interface sounds good, I think a good place to start would be to add it
>> to the context menu. I filed:
http://crbug.com/224285
Yes, that is a sensible thing to do - and what Chris' extension does. The
only difference in Opera is that the entire menu item is only there when
there is a longdesc.
> Thank you for filing these bugs.
>
>> I don't think it would fly to add a visual decoration for images with
>> longdesc unless we could give the page author a way to customize its
>> style
>
> Yes. That is important.
Right.
> of longdesc highlighting preferences including having no highlight...
My extension (I can give you the code, but it is pretty ugly and has a big
bug still) takes a slightly different approach and adds an indicator to
the address bar when there is a longdesc present. That is clickable, and
the dropdown is a list of the images linked to the longdescs.
I think at least a styling option is useful. For voice it's easier to use
something like img[longdesc]::before {…} but I agree that the visual thing
is tricky in a visual browser.
>> and come up with a solution that works on mobile, too.
>
> A User Interface idea that has been discussed for touch devices is a
> "turn the image around" transition e.g., the UI could have a flip
> transition: akin to flipping over a hard-copy physical photograph to
> read what is written on the back. Activation could be upon a finger
> flick gesture on the corner of an image or a tap-and-hold gesture for
> a touch device contextual menu.
Yes, there are various ideas about putting something on top of the image
as an indicator that would work for mobile. When notin fullscreen mode my
opera extension actually worked with their mobile extensions framework -
but in fullscreen mode you couldn't see the indicator.
Anyway, it's not a solved problem how to do this really well on small
mobile interfaces. More implementation and more experience would teach us
more about it...
cheers
Chaals
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
cha...@yandex-team.ru Find more at
http://yandex.com