Template:Click: Difference between revisions

From FIBIwiki
Jump to navigation Jump to search
New page: <div style="position: relative; width: {{{width}}}; height: {{{height}}}; overflow: hidden;"> <div style="position: absolute; top: 0px; left: 0px; font-size: 100px; overflow: hidden; line-...
 
No edit summary
 
Line 4: Line 4:
</div>
</div>
<noinclude>
<noinclude>
'''Usage:''' <nowiki>{{Click | image=myimage.png | link=PageName | width=10px | height=10px}}</nowiki>
This template attempts to superimpose an invisible link on an image, such that clicking on the image does ''not'' take you to the image description page (normal behaviour).
It's useful for small icons/logos which are representative of an article, and which a user might click on expecting to be taken to that article. Here we are using it on the [[Main Page]] for example. It's use should minimised because of the following problems.
==== Problems ====
It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations.  The technique of using [[w:CSS|CSS]] to change page content also completely breaks an article's [[w:web accessibility|web accessibility]] by contravening a [[w:WAI|WAI]] priority-one checkpoint.[http://www.w3.org/TR/WAI-WEBCONTENT/#tech-order-style-sheets]
==== See also ====
* [http://en.wikipedia.org/wiki/Template:Click Template:Click on wikipedia] where we got this from.
* [[Mediazilla:539|<span title="ASSIGNED: Allow images that link somewhere other than the image page">Bug 539</span>]] - Feature request to allow linked images without nasty CSS.
</noinclude>

Latest revision as of 15:36, 13 April 2007

[[{{{link}}}|   ]]
[[Image:{{{image}}}|{{{width}}}|{{{link}}}]]







Usage: {{Click | image=myimage.png | link=PageName | width=10px | height=10px}}

This template attempts to superimpose an invisible link on an image, such that clicking on the image does not take you to the image description page (normal behaviour).

It's useful for small icons/logos which are representative of an article, and which a user might click on expecting to be taken to that article. Here we are using it on the Main Page for example. It's use should minimised because of the following problems.

Problems

It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations. The technique of using CSS to change page content also completely breaks an article's web accessibility by contravening a WAI priority-one checkpoint.[1]

See also