accessability / handle browsers with JavaScript turned off better

[GoogleCodeExporter]

Looking through the feedback that's been submitted so far, a fair number of
people are having issues when they have JavaScript turned off.  Obviously
reworking the sites to function w/o JS is a huge task, but we should
display a noscript message telling people to turn on JS if they want to use
the site.  Right now it just displays the frame of the homepage, without
the video or search results loaded, and any link requiring JS just does
nothing.

Original issue reported on code.google.com by ehysen on 23 Jun 2009 at 2:28

[GoogleCodeExporter]

actually, this isn't so bad since we sit on top of a clean API--
just-so-happen to output plain HTML for these people.

of course, PM/UI/UX needs to select a "path" by which users
identify themselves as wanting this "plain HTML" version, to
add to the obvious eng job of auto-detecting no JS.

this is also required for some government/etc. sites that require
accessibility.  Marking Critical unless PM can make it not.

Original comment by adam.sah on 23 Jun 2009 at 7:14

• Added labels: Type-FeatureRequest, Priority-Critical
• Removed labels: Type-Defect, Priority-High

[GoogleCodeExporter]

Original comment by adam.sah on 24 Jun 2009 at 10:32

• Added labels: Priority-High
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Original comment by adam.sah on 1 Jul 2009 at 7:51

• Changed title: accessability / handle browsers with JavaScript turned off better