Re: [WSG] empty named anchors
Andy Kirkwood | MOTIVE wrote: I have come across a couple of instances of this where headings have been enclosed in an anchor, i.e. a name=anchor id=anchorh1Heading text/h1/a This causes the text colour of the heading to change when moused-over (although not a link). From an interface perspective this can be quite confusing. (A feedback cue that suggests interaction is possible when it is not). This is why a:link:hover and a:visited:hover are preferable over simple a:link :) -- -David R ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
David R wrote: Andy Kirkwood | MOTIVE wrote: I have come across a couple of instances of this where headings have been enclosed in an anchor, i.e. a name=anchor id=anchorh1Heading text/h1/a This causes the text colour of the heading to change when moused-over (although not a link). From an interface perspective this can be quite confusing. (A feedback cue that suggests interaction is possible when it is not). This is why a:link:hover and a:visited:hover are preferable over simple a:link :) Maybe I've missed some standards or accessibility point, but I'm accustomed to coding as follows: h2a name= id=/aSome heading/h2 Jumping works like a charm, and no hyperlink behaviour other than that ever shows up. Afaik, there are no problems with this method whatsoever, plus you don't rely on CSS to prevent a particular GUI behaviour. Jeroen -- vizi fotografie grafisch ontwerp - http://www.vizi.nl/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
h2a name= id=/aSome heading/h2 Or drop the anchor tag altogether. What is the browser compatibility of this: a href=#someIdOnThePageGo to Some ID/a ... h2 id=someIdOnThePageSome ID/h2 My initial tests show great support. Anyone know better? -- Ben Curtis WebSciences International http://www.websciences.org/ v: (310) 478-6648 f: (310) 235-2067 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Ben Curtis wrote: Or drop the anchor tag altogether. What is the browser compatibility of this: a href=#someIdOnThePageGo to Some ID/a ... h2 id=someIdOnThePageSome ID/h2 My initial tests show great support. Anyone know better? Generation 4 and below browsers don't play ball with it, and IE (even 6) has some problems with it occasionally (see the section User agent issue - the IE bug on http://www.jimthatcher.com/skipnav.htm) ... so it depends on your audience whether you drop the anchors. -- Patrick H. Lauke _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Ben Curtis wrote, On 20.01.2005 23:58: Or drop the anchor tag altogether. What is the browser compatibility of this: a href=#someIdOnThePageGo to Some ID/a ... h2 id=someIdOnThePageSome ID/h2 My initial tests show great support. Anyone know better? I've been told, that some Screen-Readers don't support jumping to elements with id only. Since inner site links are especially useful for SR-Users, it seems like a good idea to keep the name-attribute. Susanne -- http://sujag.de - Webentwicklung und -beratung 10119 Berlin ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Can anyone clarify? Me not :) However I'd use construction like ... h1 id=tocTable of contents/h1 ... and you're done. -- Jan Brasna :: alphanumeric.cz | webcore.cz | designlab.cz | janbrasna.com Stop IE! - http://www.stopie.com/ | http://browsehappy.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Empty link elements are not good (as Patrick pointed out)but what about named anchors (destination anchors)? They are obsolete. Refer to any id instead. Is there any reason why they should not be empty? I wouldn't be surprised if it was because of a bug in Netscape4. -- regards, Kornel Lesiski ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Focas, Grant wrote: Empty link elements are not good (as Patrick pointed out)but what about named anchors (destination anchors)? Is there any reason why they should not be empty? I'm typically using anchors like this one: a id=item_1 name=item_1/a, and can't see the need to fill them. As Kornel pointed out; 'name=' is obsolete, but some older browsers are still in need of name', and the validator won't object. It is up to us, I guess. As a sidenote: IE6 may have problems finding anchors in a page - depending on how/where it is placed. No other browsers that I know of have such problems. regards Georg ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] empty named anchors
Title: Re: [WSG] empty named anchors
One reason why you might not want to have content inside of an
anchor would be because of the implementation of stylesheets (or more
accurately how style rules have been specified).
For example if a hover rule is written for to the a
element it will be applied to content enclosed in the anchor tag (as
well as linked text).
a:hover {color: #900;}
I have come across a couple of instances of this where headings
have been enclosed in an anchor, i.e.
a name=anchor
id=anchorh1Heading
text/h1/a
This causes the text colour of the heading to change when
moused-over (although not a link). From an interface perspective this
can be quite confusing. (A feedback cue that suggests interaction is
possible when it is not).
Cheers
--
Andy Kirkwood
Motive | web.design.integrity
http://www.motive.co.nz
