Forum Moderators: open
I've used the same strategy on other sites I've built containing Flash content, at least one of which doesn't seem to have been penalized as yet. The other ones I can't tell because they're also fairly new.
So you better make sure that your <noscript> section contains a liberal number of links into your actual content. As an added benefit, that will also be helpful for those (surprisingly many) human visitors who have disabled Javascript in their browser.
I would prefer if Google would give more detailed guidelines, not just 'don't employ sneaky redirects'.
The developer had put in autodetect script for Flash - and a javascript redirection if you didn't have Flash.
Problem was - as Bird alluded - if a user doesn't have Flash - what gives you the confidence to make you think they would have Javascript (either capability, or enabled)? And we all know Googlebot doesn't!
And just to top it off - the redirected to page (assuming they could actually get there, via the JS) was a graphic without an alt tag!..... Great for a disabled user - and great for SE spiders!
Not exactly a well thought through strategy for Section 508 (USA) or Disability Discrimination Act (Australia) Compliance.
If you use <meta http-equiv="refresh" content="10; url=http://www.yourdomain.com/text-only-version.html"> - and if you put the link in for the 'impatient' to follow immediately on the page - I think everyone will be much happier.....
Sometimes, i think the only answer is to take all the 'latest versions' and all the 'plugins' away from some developers - and make them use Lynx from a dialup 28Kb modem for a while...... (if they whinge too much, you could give in and upgrade em to the 56Kb modem)... and make em test it themselves!
: )
The JavaScript redirect is within an external .js file and I've been informed that as such, the path to the redirect wouldn't be spidered. I might be wrong, but I'm assuming this "redirect" is pretty safe.
added: ... and yeah Chris_D - I'm whingeing - some people are misinformed about Flash and usability. I'm still waiting to know why Flash is a reason why a site isn't capable of being usable.
I'm still waiting to know why Flash is a reason why a site isn't capable of being usable.
Are you confusing "accessibility" with 'usability'? If you can't access it.....
Instead of waiting, a good strategy to better understand accessibility is to download eg Lynx - a text based browser, and set about trying to ascertain for yourself whether you are able to actually 'access' a range of Flash sites.
Mostly - you can't - and the problem is that there is no 'equivelent functionality' - as you described you have provided - on many Flash based sites. And its not just Flash - bad HTML, text in .jpgs etc can be just as inaccessible.
But isn't it the fact that you have provided separate text based equivelent content and linking the reason your site is viewable in a text based browser? And isn't that therefore part of the 'Flash issue' - that you had to separately duplicate your content to make your site accessible?
The W3C provides some good basics on accessibility issues. If you really want to know Patrick - start reading here: [w3.org...]