Comments on: Flash/flex accessibility and wmode http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/ Confessions of a serial code abuser Sat, 11 Oct 2008 03:09:30 +0000 http://wordpress.org/?v=2.6 By: wmode 三選一 « 就是愛程式 http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-25452 wmode 三選一 « 就是愛程式 Thu, 20 Sep 2007 09:56:32 +0000 http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-25452 [...] Flash/flex accessibility and wmode [...] [...] Flash/flex accessibility and wmode [...]

]]> By: Steve http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6620 Steve Tue, 03 Oct 2006 16:33:26 +0000 http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6620 Thanks John for the extra information. I've updated the article to include the information you've provided. Thanks John for the extra information. I’ve updated the article to include the information you’ve provided.

]]> By: John Dowdell http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6619 John Dowdell Tue, 03 Oct 2006 16:07:57 +0000 http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6619 In the default state, browser extensions (Netscape Plugins & ActiveX Controls) render directly to the screen. Many browsers and extensions now support the ability to pipe the extension's output directly into the browser's compositing buffer. This is triggered by WMODE. (Macromedia Flash Player introduced WMODE support as soon as some browsers offered it, towards version 3 or so.) But... the browser owns the final rendering then, because we don't go direct-to-screen. Different browsers have different behavior... some print upside-down, some don't pass MSAA calls through, and so on. Like other browser differences, there are few resources on the exact ways each of the various browsers handle things differently. Andrew Kirkpatrick has one of the most intensive tests of how different browsers change assistive abilities in response to different scripts and tags: http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm In the default state, browser extensions (Netscape Plugins & ActiveX Controls) render directly to the screen.

Many browsers and extensions now support the ability to pipe the extension’s output directly into the browser’s compositing buffer. This is triggered by WMODE. (Macromedia Flash Player introduced WMODE support as soon as some browsers offered it, towards version 3 or so.)

But… the browser owns the final rendering then, because we don’t go direct-to-screen. Different browsers have different behavior… some print upside-down, some don’t pass MSAA calls through, and so on.

Like other browser differences, there are few resources on the exact ways each of the various browsers handle things differently. Andrew Kirkpatrick has one of the most intensive tests of how different browsers change assistive abilities in response to different scripts and tags:
http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm

]]> By: nicolas http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6613 nicolas Tue, 03 Oct 2006 13:28:12 +0000 http://dynamicflash.com/2006/10/flash-accessibility-and-wmode/#comment-6613 And it screws up textfields and keyboard mappings in firefox And it screws up textfields and keyboard mappings in firefox

]]>