i don't have a lot of experience with this, but i do want to just add this little bit:
you can get your pages to validate if you use a javascript solution to embed your flash movies (like flashobject - http://blog.deconcept.com/flashobject/) this will allow your page to validate (and i'm assuming it will also pass the automated AAA tests) and will also allow screen readers like JAWS to access the Flash content. because of the way flashobject works, you can also have alternate content on the same page that will be displayed (and read because it's just normal html content) if the user does not have the flash plugin, or the correct version of the plugin for that matter) there's more info and a side by side comparison of different flash embedding techniques here: http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm Michael Stuhr wrote: > Rostislav Hristov schrieb: > >> @Carlos >> >> I was referring to this thread on Flashcoders: >> http://chattyfig.figleaf.com/pipermail/flashcoders/2005-February/131886.html >> >> This seems to be an interesting read: >> http://hacks.oreilly.com/pub/h/1568 >> >> >> @Micha >> >> Thanks for explaining. I have never developed such content and I have >> no idea about the problems that may appear. The situation with Flash >> and Accessibility is not that great so every option should be >> evaluated. >> >> >> >> > > well i have tried (was forced to, kinda) and it made me feel really bad :-) > > there are tons of problems, if you want to deliver accessible flash pages. > think > of scalability, color contrasts, videos for deaf people etc. pp. Not to > mention > to correctly handle plugin usage (think of xhtml-strict pages) explain the > users > who do not have the plugin why they need it, where to get it, and how to > install > it. (No: MM / Adobe's explanations not the best to say the least) use > preloaders > all over the place, explain this again to users (especially to Jaws users, as > Jaws tells you already loading states of a page (even flash pages !) :-) ) > ... > well some things have more to do with usability, but you have to think for > those > too: mobile-devices, who have no flash-plugin or only f4-alike (yes there are > still alot!), or Linux-boxes, or browsers (think of internet-cafes) where > plugins are not allowed ... so to the expectable usability-hell through > whihch > we are all here and then going comes the part of tts. > > Well thank god my boss is not on this list, so he has no idea that there > might > be a chance to do all this ;-) > > And yes i'm a flash lover too, but my daily job is to build accessible > websites, > and sorry folks, this means too often: no-flash, guaranteed! > > Flash has too many capabilitys, and if you leave those out which will lead to > 100% un-accessibility, it no more worth than html (no: d- and ajax play in > the > same league if we're talking about usability and accessibility) > > just my 0.02€ > > and this wasn't meant to flame anybody, this is just the situation which we > face > now. there might be better times in future, but i have my doubts that adobe > will > do anything better than MM. > > micha > > > > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
