Forum Moderators: open
Also, what's to stop your visitors lying.
It seems like a pointless endevour.
Chris
I was wondering if it's possible to do it the way NYTimes does, where if you don't have a cookie you don't get into the site. The cookie check could be done by browser, thus leaving the bots free to roam.
However, someone correct me if I'm wrong, but I remember seeing Ink's bot rummaging about emulating NN 3 & 4.
On an aside, I'm wondering why a billboard is OK, but a web page needs an age verification? Or is this a contest or something?
Make the age check a thin div at the top of the page. Then follow it with the rest of the successful page in another div, but make it display:hidden until the age check is completed.
You could even use absolute positioning for the age-check div so that it wouldn't have to appear first in the HTML.
AFAIK (and I could be wrong), those who are underaged
are allowed to view the site, simply not allowed to place an
order.
If this is not the case, then what about supermarkets?
May those under the legal drinking age not walk in
the beer/wine section?
Could be an issue of advertising to minors, I suppose.
But that would be getting into legalese. What is advertising
vs showin an item for sale...
We have recently asked one of our clients one of the points raised: Why do you need age verifcation on a website when there are TV ads and Billboards out there?
The response we were given was that billboards sell the Brand, where as websites make them look "Cool", "fun" etc. I assume this is because there are such things as games, interactivity.
Its not so much the promotion of the drink that seems to be the probelm, its more the promotion of it as being Fun.
I think a lot of it stems from the Hooch days, when it was accused of deliberatly targeting under agers with its cartoon labels.
It is a rather frustrating topic. Here in the UK it is slightly easier. You really just have to be seen as warning the user they have to be over the legal drinking age, where as in the USA you have to actually make the user put in their age.
But again, as was mentioned in this discussion, there is absolutely nothing stopping the user lying about there age.
We have a couple of methods to get round it. One is to use a layer over the actual page. The age check is in the layer, and the actual page behind cannot be used because of the layer, however, to the search engine it is just a layer, and it continues to read the Source code....including all links.
This seems to be an ok way.....not great by any means, but ok.
I had thought of using a cookie to detect whether or not the user had been on the page before, and if so just let them through. But cookies detect the browser, not the user. So if i were to login on a machine, then the next day a 15 year old was to visit the site on the same machine they would be allowed straight in......not good!
All your ideas are appreciated, and helpful and i will give them all a try.
Anyway, i just thought i would add my bit, please keep talking.....more ideas certainly welcome.
Webboy