On 5/7/2009 1:43 AM, Chris Dew wrote: > Do other developers consider it vital to support non-javascript > browsers for accessibility reasons? Or are people largely using ajax > regardless of accessibility, to make their apps look shiny?
It depends on who the app is for. If it's in a corporate environment where you know the constraints you're working with, then by all means AJAX away w/o fallback. Or in another extreme, maybe you can't use AJAX at all in that environment. But if it's public facing, you're probably better off constructing the entire app w/o AJAX first and then selectively put in widgets where usability can be improved. This way you're not locking out some segment of your users. Note this doesn't just apply to AJAX, but to JS in general. And more importantly, you should have valid semantic markup that can still be read w/o relying on styling if possible, if you want things like screen readers to work. -- George --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
