We've done some 508 Flash (not Flex) stuff a couple of years ago and used Jaws to test it. In our experience, Flash's Accessibility hooks were not exactly perfect and if our app changed state too much and gave too much information to the accessibility engine, it would choke and die. Eventually we got it working, but it's far from the rainbow colored magic pixie dust that Adobe would like you to think it is. Of course, that was two years ago, so maybe it's gotten better.
Like Scott said, test with a keyboard only. I'd go a little further though and turn off your monitor as well. This is what a completely blind person will experience - keyboard only, no monitor. -Cameron On Mon, Jul 30, 2012 at 4:58 PM, Dale Bronk <[email protected]> wrote: > We have a Flex 3 application where we have spent almost no time on making > it an accessible application. Any one have experience with it? I see > there are properties to set during compile to turn on accessibility, but > what tools have you used? > > What screen ready have you used? > What tool for analyzing the application and "scoring" the application for > 508 compliance? > > Any information will be appreciated. > > Dale > -- Cameron Childress -- p: 678.637.5072 im: cameroncf facebook <http://www.facebook.com/cameroncf> | twitter<http://twitter.com/cameronc> | google+ <https://profiles.google.com/u/0/117829379451708140985>
