Modern Flash development
The classic attitude towards Flash is that while it is an excellent tool for interactive visual effects when applied properly, it is a pain in the back when it comes to accessibility and semantics. This black-and-white view often leads to arguments between the Flash developers and front-end coders.
Since I’ve never really liked trench warfare, I’m glad to see that great minds have conceived clever solutions during the last years. We all know about the eternal struggle between the elements <Embed> and <Object>, the classic Flash Satay method (better but still flawed) and its modern successor SWFObject (a progressive enhancement approach) together with swfAddress.
If you’re feeling tipsy, you can also put HTML elements on top of your Flash movie by adding the following parameter:
But be careful, there are several reported problems with this method including reduced framerate.
Accessibility is still a problem with Flash, but I’m glad to see that some progress happens every year. I suppose that WPF/E will start it all over again in a year or so, but that’s another story.