http://www.standards-schmandards.com/index.php?2005/03/01/16-ajax-and-accessibility
http://adactio.com/journal/display.php/20050308163812.xml
- Original Message -
From: Maarten Stolte [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Wednesday, June 29, 2005 5:55 PM
Subject: [WSG]
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-accessibility#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
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
@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
On 6/29/05, Drake, Ted C. wrote:
re:
http://www.boxofchocolates.ca/archives/2005/06/12/javascript-and-
accessibility
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