MSAA SDK tools and screen readers are not working with release builds here: http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ However, they are working in debug builds built from the same source. This has been a problem since at least 6/22, perhaps as long back as 6/15. Not sure if there is also an issue with ATK support. Perhaps Sun can check.

Blocking any work with screen reader vendors on Windows.

This is very strange. Release builds and installers that I make from my machine don't exhibit the problem. Creature's builds consistently do have the problem. I know the problem is in accessibility.dll, which is 3k smaller for the bad version of it produced by Creature. When I copy the good accessibility.dll that I build overone in a copy of Mozilla with this bug, everything works. Even when I make my own release installer from my machine I can't produce an inaccessible mozilla. I have essentially the same build environment as Creature. The only differences are: * I'm missing -DX_DISPLAY_MISSING=1 . Doesn't look significant * I'm missing -DMOZ_BYPASS_PROFILE_AT_STARTUP=1. Doesn't look significant. * I have -DOSTYPE=\"WINNT5.1\" instead of -DOSTYPE=\"WINNT5.0\". * I'm using Visual Studio .NET 7.1 and Creature appears to be using vc98. That could be it. If it's the difference in compilers maybe we could just upgrade Creature to VC 7.1.

Bug 243313 fits the regression window. It probably exposed a compiler bug, or at least a difference between the VC98 and VS.Net7.1 compilers.

I've backed out bug 243313. We'll see what Creature does tonight.

Fixed by backing out bug 243313.