Too often universal accessibility is of lowered priority on projects.
Heavy Javascrpiting and DHTML cocktails otherwise known as AJAX (or for the dot commers) Web 2.0 web applications require some special consideration when planning UI.
I thought I'd pass along some handy dandy information for my own and anyone who happens upon this posts edification.
Consider this.
- There are legal aspects to providing Universally accessible interfaces. This came about because of lawsuit filed in the UK regarding a blind individual who was having difficulty using a banking site with a screen reader (I'll tell you more about Screen Readers later). So when planning a commerce site or mobile application for the European market or one that could possibly used for commerce in the UK (ie; accepts Euros for transactions) consider accessibility in all aspects of the design.
- Many of the deeper issues with DHTML can be resolved with the manner in which they are codes but it is helpful for UX, UI and Visual Design people to know about accessibility because it can aid in create a successful and usable design from the very beginning of a design instead of as an afterthought. A good designer, as a good architect knows, you need solid foundation to build a successful product.
- Designing for accessibility is not that hard. Once you have the awareness it becomes second nature.. Before design school we didn't know what a grid system was and why it was important... now it is just a part of what you do, without even thinking about it. Universal Design is pretty much the same principal.
