[Bug 25404] ALT Guidance bugs

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

--- Comment #2 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to dmacdona from comment #0)
> Here are some bugs filed against the ALT guidance document that also apply
> to HTML5
> 
> 
> 1) I think screen reader users should be explicitly informed that
> information below is the alternative... rather than deducing it from the
> heading above the alternative.
> 
> alt="Flowchart: Dealing with a broken lamp.">
> 
> I would add "full description below"
> 
> alt="Flowchart: Dealing with a broken lamp. Full description below.">
> ========

The image is in a link

<a href="#desc"><img src="flowchart.gif" alt="Flowchart: Dealing with a broken
lamp."></a>

the user can follow the link to the structured representation of the flow chart



> alt="Bar chart: Average rainfall in millimetres by Country and Season."
> 
> Same here
> 
> alt="Bar chart: Average rainfall in millimetres by Country and Season. Table
> of data below."


I think that this would be better handled by wrapping the img + table in a
figure (+figcaption element) will do this.


> 
> 2) I'm not sure of "more than a couple of sentences" being the guidance for
> providing a long text alternative. I've always understood it to be if it
> requires more than about 100 words, OR if there is a necessity to structure
> it, then a long and structured description should be provided. A couple of
> sentences means about 20 words. Do we really want people to start requiring
> a long description if the alt is more than 20 words? Remember, the general
> public will take this document as the final word... I would like other's
> thoughts on this.

will tweak

> 
> 3) Also I think we need an example of the long description immediately
> following the image, where it is hidden in an expandable tag such as the
> Details/Summary (or a JavaScript fallback) .... every developer I know
> resists long text following an image because they don't want to give up the
> page real estate.

ok will add

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

Received on Saturday, 17 May 2014 08:26:17 UTC