[Bug 21566] User agents must present longdesc through normal interfaces.

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

--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
In reply to comment #4:

> it would be hard to argue that an image properties dialogue is not
> part of "the normal interfaces". (I think that would be inconvenient for
> users, but that's not the same as being non-conformant).

and at the end of comment #4:

> I'm quite strongly opposed to reducing the level of requirement just so
> everyone can claim conformance without actually doing what a spec asks -
> that gives a lot of conformant, implementation but at the expense of any
> useful interoperability.

Comment: Nevertheless, if image properties dialog is considered a "normal
interface", the bar *would* be so low that "everyone can claim conformance"
quite easily. May be the bar should also be so high that it is interesting to
implment, though ...

It seems to me that current versions of Opera and iCab, would then meet this
bar easily, since the allow access to longdesc via contextual menu. And also,
at least iCab, uses the mouse pointer to signal presence of longdesc.

> And no, it is explicitly not about Accessibility APIs - there is a separate
> requirement for that which is currently at SHOULD rather than MUST.

Comment: Keyboard accessible - is that an A11Y API thing? Or an 'normal'
interface thing?

Speaking more directly at this bug report, may be the spec should require that
vendors that implement this extension make sure to not implement it in such a
way that one *MUST* use AT in order to access a longdesc?

>NVDA resisted implementing longdesc for *years* because they
>hoped that browsers would do what this is asking. 

An image properties dialog would hardly be enough for NVDA. What would be
enough? Perhaps the only thing that would have helped NVDA would have beeen to
have keyboard access to the longdesc?

Just as an idea: Would it be possible to give keyboard access to the @longdesc
URL *if* the image has the tabindex attribute set? The image did not need to be
clickable. But the longdesc URL could be made accessible via the Enter key
provided that the image has focus. Already today, certain aspects behave
differently based on whether one uses 'keyboard access' or 'mouse access'.
Think of hover ...

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

Received on Thursday, 4 April 2013 12:51:28 UTC