On Sep 2, 1:18 pm, marcelo <[EMAIL PROTECTED]> wrote: > Is this a joke or has my logic not had enough coffee today? :-) > If people cannot see a map because they are blind, then they cannot > see text either.
But they can use screen-reading software like Jaws or Browsealoud, which turns text into speech. There are a couple of potential obstacles to this with Google Maps API. One is whether the default GDirections textual table is compatible with readers -- it needs to be formatted correctly. This can be overcome by a method such as Mike uses at http://econym.googlepages.com/steps.htm where you can use the data to build exactly what you need. A more major problem is likely to be the asynchronous nature of GDirections, where a page is built using Javascript. You could try Mike's page which I've linked to and see how the reader software copes. 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 -~----------~----~----~----~------~----~------~--~---
