[Bug 21565] Should it be an error to use @longdesc on presentational images? And/Or should it _affect_ the role of the image?

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

--- Comment #9 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to comment #8)
> Hmm. As Leonie points out in
> http://tink.co.uk/2011/06/text-descriptions-emotion-rich-images/ the problem
> is really that we have a very simplistic idea of what "presentational" is.
> 
> My rough thinking is that "presentation" is stuff that isn't really
> necessary for a functional use of content. However, there are times when
> people want to pay attention to the presentation. Indeed, screen readers can
> already present presentational things like font information because it can
> be of interest (or even important to understand), but they don't do it by
> deafult because it is overkill for the most common use scenario.
> 
> I suspect the best answer isn't to change the way the role is determined,
> but for implementations to be a bit more flexible with "presentation". As I
> already noted (and Leonie noted in her blog post) things like stock
> photography and background photographs are often of interest even if they
> are not really the point of a page (after all, that is why the designer put
> them there in the first place).
> 
> On a technical level, current implementations would not be able to conform
> to both a requirement that longdesc is valid on

OK but how does that equate to implementation?

the current implemnentation of role=presentation is supported across browsers
and does was i said - removes the element from the acc tree, so AT that use the
acc tree don't get it or its attributes.

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

Received on Thursday, 4 April 2013 12:53:03 UTC