Each website has an optimal design that fits perfectly to its thematic, requirements and visitors' type. For example, a web site offering e-cards will certainly need to catch the visitors' eyes, using images, animations and interactivity, while a site dedicated to science, teaching or investigation may not need any of those to show up their information and content .
The amount of animation or interactivity will certainly affect the accessibility of the web page given that the technologies used to provide this type of content are typically not supported by user agents or many times not designed for people with disabilities. To consider how many people you could be letting behind I will base my study on the statistics of this site (HTMLQuick.com) which is completely accessible and provides a lot of textual information.
Flash is a great way to build animations and interactivity but could also be a big accessibility problem. Creating a website completely in Flash could let out a 2.78% of the visitors and make the site completely empty for search engines, which may be your primary inconvenience.
Many sites will look at Flash as a primary necessity while others may only use it for animation or will not use it at all.
– If your site does not need it, then try to use it only for animation or providing rich alternative texts.
– Avoid building menus in Flash, as user agents not supporting it will not be able to follow their links.
– Export the swf files using the lowest version possible. Only a 69.2% of the visitors use the latest version. The rest 29.03% will have to download before playing the movie.
– Try to make the movie size as little as possible so people do not get bored waiting for the page to load. There are still an 11.83% of visitors using dial-up connections.
– If possible use it only for not necessary interactivity and functionality.
– Otherwise, provide alternative static content in the "noscript" tag.
– Do not make it necessary to follow a link. Use the "location.href" command as the "onclick" event in a static link ("a" tag).
Frames are nice, but should be definitively avoided. While most of the user agents support frames, search engines, as well as blind people, could have been seriously confused when trying to relate the …