On Feb 20, 7:42 am, "David C." <[email protected]> wrote: > > Ross, it's not a problem of the browser itself; it's a matter of > accesibility. In order to have the double-A level of web accesibility > (http://www.w3.org/WAI/), the site must be operational without > javascript.
The point of the "no javascript" rule is so that text browsers and screen-readers can cope. Given the nature of a map, its application to a page containing an API map is moot [in my opinion, anyway] Even using <noscript> and a static map, there *is* an issue with direction-finding, as that requires Javascript to work and can't be prepared server-side to be delivered to text browsers. Add your star to issue 235. http://code.google.com/p/gmaps-api-issues/issues/detail?id=235 Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
