I'm trying to come up with a good solution for how my Gears based
projects should degrade. I want decent accessibility and search bot
friendliness, but at the same time, my small business clients are not
interested in spending a lot of money on development for fringe cases,
so I have to justify every cent spent, and being able to depend on
Mochikit makes life a lot easier. My current idea is this:

- javascript checks out browser version, viewport size, etc
- if viewer has JS on and CSS and browser greater than current - 1, the
rich media version of the site is seen
- else, the viewer sees a plain text version of the site with dom
structure friendly for lynx/scraping/accessibility/google ( Content
first, accessibility friendly tags and structure, etc )

The above strategy means that I can avoid ugly hacks in the css and in
the DOM structure by having JS functions do any cross browser and screen
size adjustments. The downside is that it gives viewers with no JS
enabled a plain text site. My feeling is that this is a good compromise
that prevents broken site viewing, IMHO worse than seeing a plain text
site and a message saying "You are viewing the plain text version of
this site. The rich content version requires javascript and css to be
enabled, and a browser of miniminum IE6, Firefox X.X, etc "

My question though, is how many people out there am I likely cutting out
or going to annoy by saying plain-text *or* JS+CSS, but no CSS without
JS? I have never worked in the regular office industries, so I have no
real idea how many people view sites behind javascript blocking.

Opinions on the above? Strategies that others follow?

Thanks
Iain


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to