Pardon a newbie perspective, I like to show my skip navs a few pixels
up, but visable, useful to see it as well as have it there, I hide it
with a no show in the printing stylesheet. It allows easier keyboad
navigation I think. I'm not sure of any SEO penalty for -9000 pixels,
why not just a few pixels north of absolute screen top?
<p class="SkipNav">
<a title="Skip the Menu and go straight to the start of the page
Access Key Ctrl+0" href="#skipnav" name="Top" accesskey="0"
tabindex="1">Skip Nav</a>
</p>
Stylesheet
.SkipNav{color:#330099;font-size:60%;position:relative;left:.2em;text-
align:left;font-family:Georgia,"Courier New",Times,"Times New
Roman",serif;margin-top: -.2em;margin-bottom:
-1em;text-indent:-2em;line-height:30%;}
I've been working on seven different versions, trying to line up the
homepage with div instead of tables in all version I can find of Win
and Mac browsers, Javascript switches stylesheets.
Yikes! I was not ready for this yet, but they should be almost closely
aligned, some work to do yet. Please let me know if there any major
bugs, Safari can put BODY:after content at the top of the body the muck
up all that absolute positioning, I tried em's for flexible font
sizing, but had to go to pixels for accuracy, hope I am almost there.
My pithy advice, make the skip nav a few pixels up, but just visible
with a good rollover or onfocus title.
Thanks for the postings you all let me listen in to and learn from.
Tim
http://www.hereticpress.com/index.html
On 18/07/2006, at 2:22 PM, Lachlan Hardy wrote:
On 7/18/06, Paul Bennett <[EMAIL PROTECTED]> wrote:
text-indent: -9000px;
may get our site penalised by search engines.
People often talk about this. Does anyone have any specific references
of it actually occurring? I've not seen it yet
I can live with this, as the content is still accessible.
Question is, what am I missing? Is it ok to do this, or is there some
horrible hidden issue I'm not aware of?
Not a hidden issue, particularly. Just that your image will not resize
when people resize their text. It depends how concerned you are about
that
In such situations I typically use, sIFR. It usually meets my client's
requirements for headings in atypical fonts, while still providing
what I consider an acceptable level of accessibility. Everyone's needs
are different (as is said so often on this list), so it may or may not
meet your needs this time (or ever)
If you haven't looked at it before, see
http://www.mikeindustries.com/sifr/
Although you might also be interested in the development of sIFR 3.0 -
http://novemberborn.net/sifr3
Lachlan Hardy
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
The Editor
Heretic Press
http://www.hereticpress.com
Email [EMAIL PROTECTED]
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
