Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Google Webmaster Help
Home
About this group
Join this group
Message from discussion Using CSS to hide text
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Sam I Am  
View profile  
 More options Jun 12 2007, 7:18 am
From: Sam I Am
Date: Tue, 12 Jun 2007 04:18:35 -0700
Local: Tues, Jun 12 2007 7:18 am
Subject: Re: Using CSS to hide text
Print | View thread | Report this message | Find messages by this author
Susan, thanks so much for stopping by and answering the question! I
noticed a few other sites picking up on the answer already and I can
imagine it will trickle down into the standards based community quite
quickly too. It's good to know you have nothing to worry about if your
intent is solid, but that even if your intent is solid and you have a
few of these gray areas piling up it might result in something. At
least that gives someone 'in the doghouse' something to look at if the
cause for this might otherwise not be clear.

Given that further reading up on this method shows that there's quite
a few caveats when it comes to screen readers anyway (although it's a
great solution for mobile browsers who are an increasingly important
group to look at) I'm going to take a fresh look at a text based
solution as well. Chris, thank you for the pointers. It does seem like
a more viable alternative, although I'm now thinking avoiding all the
extra spans is the most semantically correct way to go in the long run
anyway. It's just a shame there's not more alternatives in terms of
fonts really!

On Jun 11, 5:39 pm, cass-hacks wrote:

> > I don't see that Google can progammatically verify what CSS does
> > anyway.  First it would double the crawling bandwidth needed, and
> > secondly it would be trivial to serve the Googlebot with an innocuous
> > CSS.

> I don't see how it would double any bandwidth, if Google indexes the
> pages it already has everything referenced in the page.

> And of course it would be trivial to serve the Googlebot an innocuous
> CSS but the same could be said for serving the bot anything innocuous
> while serving everyone else something different.  CSS, HTML,
> Javascript, wouldn't really matter.

> I could think of a trivial brute-force method for determining to a
> certain extent what CSS does, render the page and then run an OCR over
> it.

> I'm not saying how likely it is that Google does that but where there
> is a trivial brute-force method thought up by a Neanderthal, like me,
> there is usually a more elegant and efficient method possible to
> someone who knows what they are doing, e.g. Google-heads.

> Craig


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google