Caveat - sorry I should have said this in my earlier email - we don't have Flash 8 here.
Screenreader support, currently only Jaws and Window Eyes work with IE and flash afaik, is still a moving target. For example, Window Eyes would read and re-read dynamic textfields each time the field's content changed, getting into an infinite loop in some cases. Now that has been fixed, but it means that important changes in the field's content don't get re-read. Since a lot of the work we do reuses textfields, that's a problem. More importantly, addressing screen reader users does not make a site accessible - providing for all the other groups (deaf, photo-epileptic, poor vision, motor disabilities, and cognitive disabilities) makes much more work in Flash than html. (I say this is a Flash lover, btw) I think, and many of our clients agree, that if we create a Flash site, we have to compromise accessibility. If accessibility is important, then we build in html (with spatterings of flash) Cheers James Carlos Rovira wrote: >>Flash is intrinsically inaccessible > > > Why do you state that?. In Flash we have a lot of more resources to > make the site accesible and we can implement accesibility for screen > readers through IE. are I missing something? please give us more > feedback about this topic... > > > > > 2005/12/15, James Knight <[EMAIL PROTECTED]>: > >>I come across this issue on a fairly regular basis. >> >>There are people who think that, as long as you tick all the WAIC boxes, >>your website is accessible. >> >>My opinion is, even with html, you can make a site that passes the >>tests, but isn't really accessible. >> >>Accessibility is a state of mind (;-)) - put yourself in the position of >>a user who needs an accessible site for a while, and that doesn't just >>mean people who are completely blind: I wear glasses when my eyes tire, >>and I really appreciate sites that ask for less effort from me. >> >>I don't think we can say, in clear conscience, that our site is ok just >>because the html that holds the flash object is well-written. Flash is >>intrinsically inaccessible. Therefore, this is an instance where we must >>make a non-Flash version of the site to get around the problem. >> >>I hope this helps, and I hope that MM/Adobe is addressing the issue? Guys? >> >> >>Thanks >>James >> >>José Francisco Rives Lirola wrote: >> >>>On 15/12/2005 Carlos Rovira wrote: >>> >>> >>>>Ok José, >>>> >>>>I will if I get something ; ) >>>> >>>>Thinkg about it...if you have a website build entirely with Flash and >>>>only one HTML wrapper that is valid for triple AAA validators...can >>>>we consider the application valid in that context?, As I'm a newby >>>>for this kind of stuff, I don't know if what I'm saying have some >>>>sense... >>> >>> >>>Well, if i insert the Flash object tag inserted with Dremweaver and i check >>>if it is HTML valid the answer is not. I have to change <object> tag >>>declaration to >>>validate the standard. I supposed that with tiple AAA it is the same >>>;-), if you change >>><object> tag refered in triple AAA documentation then you will check a >>>valid HTML >>>AAA :-P but anyway if your flash is not prepare for accesibility this >>>method only is good >>>for to get a pretty medal putting the AAA valid banner but really you >>>don't help to >>>people with accesibility problems :-( >>> >>>Regards. >>> JFRL >>> >>> >>>_______________________________________________ >>>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 >> > > > > -- > ::| Carlos Rovira > ::| http://www.carlosrovira.com > > _______________________________________________ > 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
