diff options
Diffstat (limited to 'wired/old/published/Webmonkey/Monkey_Bites/2007/01.29.07/Wed/tut.txt')
| -rw-r--r-- | wired/old/published/Webmonkey/Monkey_Bites/2007/01.29.07/Wed/tut.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/wired/old/published/Webmonkey/Monkey_Bites/2007/01.29.07/Wed/tut.txt b/wired/old/published/Webmonkey/Monkey_Bites/2007/01.29.07/Wed/tut.txt new file mode 100644 index 0000000..c3e3be4 --- /dev/null +++ b/wired/old/published/Webmonkey/Monkey_Bites/2007/01.29.07/Wed/tut.txt @@ -0,0 +1,11 @@ +There are times when Ajax makes the web a lovely place and there are times when it drives even the most progressive of web surfers a bit batty. It's the J. Yes Javascript is main problem in Ajax since not all browsers handle it the same and some users disable it altogether. + +But that's no reason to abandon Ajax completely. The secret is to make sure your Ajax functionality degrades gracefully, that is, users without Javascript or whose browsers don't quite support what you're doing should still be able to accomplish the same tasks without the Ajax. + +There is no magic bullet tutorial I can point to for accessibility issues with Ajax, every situation is different. A good rule of thumb is to design your app without Javascript and then start adding it in afterward, but in some cases that might not be practical. + +Because there's no cure-all, today we have not really a tutorial but a list of tutorials and articles that address various aspects of Javascript usability. Max Kiesler has rounded up 40 tutorials in an article entitled [How to Make Your AJAX Applications Accessible][1]. + +The issues addressed in the tutorials in Kiesler's round-up won't solve all the problems and in some cases there may not be a way to solve certain issues, but at least it's a start. + +[1]: http://www.maxkiesler.com/index.php/weblog/comments/how_to_make_your_ajax_applications_accessible/ "How to Make Your AJAX Applications Accessible"
\ No newline at end of file |