I tend to treat screenreaders as Javascript ignorers, but I know in certain cases this isn't the case. I tend to build my sites as flat HTML/CSS plus back-end technology and then add the event handlers, additional buttons etc using scripting. I'd like to know if screen readers are partially parsing the code and falling flat. It makes much more sense to hand users a flat text page with additional contextual headers and description that you then go on to hide for users who get meaning by visual proximity for example. Hopefully that makes sense. Thanks, Dan. On 6/19/07, John Farrar <[EMAIL PROTECTED]> wrote:
My understanding is that with screen readers you need to treat the pages like there is no JS on the page. The jQuery modifications would not be compliant. (Thus technologies like EXT, again from my understanding, are not 508 compliant.) Benjamin Sterling wrote: > Hey Guys and Gals, > I am doing some research on Ajax and 508 compliance and wanted to get > everyone's take on the issue. Does anyone have any experience with > getting screen readers to pick up on changes to the DOM? > > I am compiling a list of sites that discuss the issue, feel free to > see what I find: http://del.icio.us/kenzomedia/screenreaders > > I go to the Dept. of Ed in a few weeks to their accessibility > department, where the majority of the people that work there are blind > or def, to see/hear what some of the website look/sound to them. We > had two of our developers go a year ago and it was very eye opening to > them. > > -- > Benjamin Sterling > http://www.KenzoMedia.com > http://www.KenzoHosting.com
-- Daniel Eastwell Portfolio and articles: http://www.thoughtballoon.co.uk Blog: http://www.thoughtballoon.co.uk/blog
