25404 2014-04-21 18:25:25 +0000 ALT Guidance bugs 2015-06-05 15:01:13 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED FIXED a11y P2 normal --- 1 david100 faulkner.steve faulkner.steve lwatson mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 104113 0 david100 2014-04-21 18:25:25 +0000 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."> ======== 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." 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. 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. 104824 1 lwatson 2014-04-30 17:30:37 +0000 On behalf of bug triage. Dave, can you seperate the three issues here into separate bugs? It'llmake them easier to triage and track. Thanks. 106242 2 faulkner.steve 2014-05-17 08:26:16 +0000 (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 107429 3 robin 2014-06-06 09:40:14 +0000 I believe all the changes related to this bug have now been backported to CR; anything missing? 107436 4 david100 2014-06-06 14:00:31 +0000 Any further follow up on any of these issues I will take to 5.1 ... we can close out 5.0