Full Text Search: The Key to Better Natural Language Queries for NoSQL in Node.js
Problems with Flash
Accessibility One of the major problems with Flash is that it presents difficulties for many people with disabilities. For some the issues are in translation from Flash to the screen reader. For others the big problem is the lack of keyboard navigation options in most Flash animations. For those who cannot use a mouse, an animation that requires mouse clicks is of no use.
If you think that accessibility isn't important for your US-based Web site, you might want to think again. The Americans with Disabilities Act (ADA) was specifically extended to Web and other electronic media in the enforceable policy codified in 2001. Since then there have been a few high profile court cases, including the 2004 case in New York against Cendant, Inc. (owners of Ramada.com and Priceline.com) and the 2006 case against Target. And even if the ADA doesn't apply to you, it makes sense to think about this audience when you create Web content, since the tools for online accessibility can be a cost effective way to do good and generate more business at the same time.
It's possible to create somewhat accessible animations with Flash technology, but there are several problems with it. For one thing, Flash accessibility tools are only available to those using Windows and Microsoft Internet Explorer. For those using a non-IE based speech browser or a speech browser on another platform, Flash is unusable. There's also a problem with Flash animations, even with the best accessibility options, because every time the screen changes, the reader returns to the top of the page. You can imagine, then, how your lovely animation sounds to your sight impaired users.
Search Engine Friendliness The next major problem is Flash doesn't work well with search engines. While there are capabilities within search engines to index Flash, they do it poorly. The Macromedia Flash Search Engine SDK has been around for years, but you're unlikely to see any Flash-only Web site show up properly in a free search engine. The same issues that make Flash inaccessible to people with disabilities also makes it inaccessible to indexing spiders. For all intents and purposes, spiders are deaf, dumb and physically unable to navigate fully with a mouse.
For an example of this problem, have a look at the DecorStock.com web site, an online boutique art stock agency with a collection of digitized work catering to Interior Designers and the Hospitality Industry. Type in "decorstock" on Google and you'll get a listing for the Web site and a few articles about the company. Type in "site:decorstock.com people" and you get no returns. Try "stock art fine" and you'll get bored of clicking through pages before finding DecorStock.
Due to the indexing issue, top search engine information sites still advise Flash-only sites to create secondary HTML sites so they won't disappear into thin air. DecorStock is having to create a new search engine optimization strategy, where their Flash site is supplemented by a spider-friendly browse index of the artwork in their database.
Poor degradation The next major issue for Flash is it doesn't fail well. When a Web application is said to degrade well, it means that even if an end user doesn't have the latest and the greatest software, they'll still have some content, and will be able to interact at some level with your application. Unfortunately, if a user doesn't have Flash at all, or if they don't have the right version of Flash, they'll get nothing but a hole where Flash ought to be.
One of the main reasons to use Flash is it allows you to create rich, interactive multimedia experiences on the Web that work across the major browsers in all the popular operating systems without the need to test your content on each platform. If Flash works on one platform, it will work on all platforms that have that version of the Flash plugin.
However, that ignores the fact that there are various reasons why someone might not have the same version of Flash on their system, or any Flash at all. Plugin versions aren't always released for all platforms at the same time, and some less popular platforms can be one or two versions behind. The user may be a disabled person who has already learned that trying to run Flash makes it harder to navigate a page. The user may be on an office or school computer where Flash has been banned. And users on some Linux distributions or BSD, especially those who are running their *Nix on an x86-64 architecture may not have the option of installing Flash at all. No matter what the reason is for the Flash-less browser, you want users to stay at your site.
One can even argue that Flash helps lock in existing platforms and slows the uptake of new ones because of the time lag in developing plugins for the new platforms. It also punishes those who are early adopters of systems that don't include the non-standards compliant Flash.
Killing the Proprietary Plug-In
About the Author
Lisha Sterling is a partner at the Israeli Venture Technology firm http://www.SparkThing.com. She has been working in Web development and e-business consulting since 1994. She has a passion for usability and accessiblity in new technology and likes to read human factors research in her spare time.
This article first appeared on WebReference.com.