(Flash CS3 using ActionScript 3) Not sure if anyone's done something similar, but am hitting a serious frustration point. If I'm overly wordy, I apologize. I'm working on a project where I need to create a modal menu dialog that must be accessible, preferably telling MSAA that is is an actual dialog, has a title bar, close button and exposes it's child controls (text and buttons). The window is an external swf (typically created by an artist, wired by me at runtime), loaded in via a loader, and the loader.content pulled out and added as a child of the main view class.
I've been working for a day or so at creating my own MenuDialogAccImpl class, based off the Flex TitleWindowAccImpl. The problem is this: If I use a customized version of this implementation, ACCExplorer ignores the contents of the swf, only reports the existance of the title bar and a "Dialog" -- names/roles/states specified by childIDs 1 & 2. Event worse, these are "ghost" entries in MSAA that don't actually reflect the actual controls in the swf. Without an Accessibility Implementation, the items appear to MSAA with no parent-child relationship, and the MenuDialog is a simple graphic. I've looked at all of the classes in the Flex mx.accessibilty package, and the Flash flash.accessibility and mx.accessibility package (which are incidentally for AS2) and the vast majority of these are built for simple, non-container components. TitleWindowAccImpl and PanelAccImpl are both overly simple and nearly identical, and neither has any obvious code for dealing with the actual children of the window itself. I feel like I'm missing something basic here. How would a container expose it's children to MSAA? Flex obviously does this, but I can't find the code that would have this effect -- the children are wrapped in the "Dialog" object and that doesn't map to an implementation. Is there some code in flash.accessibility.AccessibilityImplementation that handles containers and exposes the children to MSAA. Unfortunately, nothing I've tried has worked. The only solution I can think of so far is not a workable one: To manually iterate each visible child of the MenuDialog from within the MenuDialogAccImpl and manually hand that item over to MSAA. Thing is, those children have their own AccImpl (SimpleButton, text, etc) and doing things this way breaks the connection to that object in MSAA. On top of that is the fact that the menus are fairly graphical ordeals, and I cannot predict the contents -- the app is used to deliver thousands of courses. Seriously frustrated and begging for help. Thanks folks. Jer _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
