rel-longdesc - Revision history

Komputist: /* The longdesc microformat, as described in W3 bug 10434 */

2010-09-03T04:20:26Z

The longdesc microformat, as described in W3 bug 10434

← Older revision		Revision as of 04:20, 3 September 2010
Line 9:		Line 9:
	[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed in that bug, will be taken into this microformat.		[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed in that bug, will be taken into this microformat.

	Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)		Here is a summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

	== see also ==		== see also ==
	* [[existing-rel-values]]		* [[existing-rel-values]]

Komputist: /* The longdesc microformat, as described in W3 bug 10434 */

2010-09-03T04:20:06Z

The longdesc microformat, as described in W3 bug 10434

← Older revision		Revision as of 04:20, 3 September 2010
Line 7:		Line 7:
	== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==		== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==

	[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed that bug, will be taken into this microformat.		[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed in that bug, will be taken into this microformat.

	Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)		Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

Komputist: /* see also */ Added pointer to W3 bug 10434

2010-09-03T04:19:39Z

Tantek: stub - point to John Foliot's proposal

2010-08-27T15:49:18Z

stub - point to John Foliot's proposal

New page

{{stub}}

Proposed by John Foliot in a [http://www.brucelawson.co.uk/2009/alternate-text-in-html-5/#comment-614001 comment on Bruce Lawson's blog].

...

== see also ==
* [[existing-rel-values]]

← Older revision		Revision as of 04:19, 3 September 2010
Line 4:		Line 4:

	...		...

			== The <code>longdesc</code> microformat, as described in W3 bug 10434 ==

			[http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c4 Bug 10434] against HTML5, describes how <code>rel="longdesc"</code> could be used to improve the advice found in [http://www.w3.org/TR/WCAG20-HTML-TECHS/G73 WCAG 2.0’s Technique G73]. Hopefully the ideas expressed that bug, will be taken into this microformat.

			Here is summary of what that bug says: <code>rel="longdesc"</code> allows authors to not only use adjacent links as description links (adjacent links are the only links which WCAG20/G73 suggests being used as ''description links''). <code>rel="longdesc"</code>, in contrast, would permit authors to also use all other link kinds: image maps, placing a link in the fallback of an <code>object</code> element or even — voila! — permit authors to '''wrap''' the embedded object in a link. (Can you believe it: WCAG 2.0 does not seem to mention that one can wrap the embedded object in a link element!) With a <code>rel="longdesc"</code> link, one should not even need to use 1 pixel wide images as a way to hide description links (yes, hiding links in "a small image" is in fact something which G73 suggestes.)

	== see also ==		== see also ==
	* [[existing-rel-values]]		* [[existing-rel-values]]