- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Wed, 9 Mar 2011 08:17:11 -0500
- To: ng@tjkdesign.com, w3c-wai-ig@w3.org
Thierry wrote: > The problem is that many authors use "transparent" or "opaque", because they do not want the object to hide other elements on the page (i.e. drop down menus). Yes, I'm well aware the issue. Unfortunately there is no immediately solution in order for the Flash to expose accessibility information. JAWS 12 changes the wmode dynamically when JAWS is running and it sets it to "window" but as you know that can have a dramatic effect. One solution that I recommend is to either detect the presence of the screen reader or offer an accessibility option which renders the same page with wmode set different. This would mean that in accessiblity mode content would need to be position different so it didn't appear cut-off behind the Flash movie but allows for different users to access the same content. For example, a drop down menu that normally would appear over the Flash content would appear horizontally above it and push the Flash content down. > I came up with a technique that allows dynamic resizing of videos. This means that if the container is set in EMs, the video can increase/decrease its size (keeping the same aspect ratio) in relation to the user's text-size settings. Yes, sounds very nice. I've played around with this technique for Flash content in general (non-video) by watching the size of the other content change and using the external interface to resize the Flash content. Flash is nice in that regards compared to Flex that it allows for this type of resizing quickly and also allows for zooming based on the IE zoom settings. Jonathan
Received on Wednesday, 9 March 2011 13:17:46 UTC