After reading this post, I began thinking that the solution may be to seperate javascripts into basic and advanced sets. Just as we import advanced style sheets to avoid confusing early browsers, perhaps we can set an option to turn off advanced scripting.
I could see the option acting much like a style sheet switcher that sets a cookie disabling advance.js but allows basic.js to set cookies, etc. This would allow the screen-reading visitor to view my site better without worrying about disabling functions in the next site by disabling javascript globally. It also would allow us to provide core functions and disable the layout based scripts. Are there any JavaScript people on this list that could comment? Ted -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maarten Stolte Sent: Wednesday, June 29, 2005 2:51 AM To: wsg@webstandardsgroup.org Cc: wsg@webstandardsgroup.org Subject: Re: Re: [WSG] AJAX and accesibility Hi, thanks for the replies, I'm reading the three articles now, and they seem very useful. regards, Maarten -----Original Message----- From: James Denholm-Price <[EMAIL PROTECTED]> To: wsg@webstandardsgroup.org Date: Wed, 29 Jun 2005 09:21:01 +0100 Subject: Re: [WSG] AJAX and accesibility Check out Derek Featherstone's follow-up to his talk at @media for some interesting viewpoints: http://www.boxofchocolates.ca/archives/2005/06/12/javascript-and-accessibili ty#more-72 1. You probably always have to do the "back end" stuff anyway, even if you can process lots of stuff that used to be "back end" on the client using AJAX -- what if your most important visitor has JS disabled or something (his firewall mabe?) breaks AJAX? 2. Some screenreaders DO detect JS-driven changes to the DOM (e.g. JAWS using IE) but I don't think it's definite what they see and what they don't and as far as AJAX is concerned it's early days :-) Just my 2p ... James On 6/29/05, Maarten Stolte <[EMAIL PROTECTED]> wrote: > Hello, > > I'm trying to find out if there are any resources on AJAX and accesibility. > It seems to me that if I would employ AJAX technologies on my site to enable a richer application experience, I would still need to code for non-JavaScript useragents . I also think that with screenreaders, lots of AJAX tricks would be hard to parse, even if such a reader would have JavaScript. > > Do these things hold true, and are there other things that I need to take into account? > > regards, > > Maarten Stolte ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
