Dennis Bathory-Kitsz / 05.1.15 / 08:28 AM wrote: >And while Andrew is working, he should meet the World Wide Web Consortium >or U.S. Section 508 accessibility guidelines (essentially the same), which >means the site will work with speech and Braille readers and other >accessibility and text browsers. No special coding is needed -- in fact, >you need only correct coding and the avoidance of proprietary inaccessible >techniques (such as Flash, Java, and Javascript) for essential components >such as navigation
I don't think you want to be strict with W3C 508. They requires most good ones but few are unnecessary to me. I do often check against it since it's a free service, but I am much more selective on the result. And.. Jari Williamsson / 05.1.15 / 08:11 AM wrote: >Some applications have tools to scan for browser compatibility. At least >DreamWeaver has this. Ur, no. It won't work especially against Mozilla flavors. DW has piles of bugs. In fact, that is all about these applications. It is much safer to hand-code to be compatible across multi-platform. You can't trust let these application does coding for you. This is all the same for building any application. I do fair amount of web dev (don't check my site which is the last I give attention so it's a mess, garbage accumulation since 1997 :) and I always check against: Win IE5, IE6, NS4.7, NS7 Mac IE, NS, Firefox Linux Mozilla, Konqueror -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com> _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
