Remove code that enables renderer accessibility based on the SPI_GETSCREENREADER parameter.

Update chrome frame so that its test automation can still use renderer accessibility.

BUG=55902
TEST=none

Review URL: http://codereview.chromium.org/3383010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59899 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 9 insertions, 0 deletions

diff --git a/chrome_frame/utils.cc b/chrome_frame/utils.cc
index 80095428..2ddc3c9 100644
--- a/chrome_frame/utils.cc
+++ b/chrome_frame/utils.cc
@@ -74,6 +74,10 @@ const char kAttachExternalTabPrefix[] = "attach_external_tab";
 // are handled by the chrome test crash server.
 const wchar_t kChromeFrameHeadlessMode[] = L"ChromeFrameHeadlessMode";
 
+// Indicates that we are running in an environment that expects chrome renderer
+// accessibility to be enabled for use in automation tests.
+const wchar_t kChromeFrameAccessibleMode[] = L"ChromeFrameAccessibleMode";
+
 // Indicates that we are running in an environment that wishes to avoid
 // DLL pinning, such as the perf tests.
 const wchar_t kChromeFrameUnpinnedMode[] = L"kChromeFrameUnpinnedMode";
@@ -960,6 +964,11 @@ bool IsHeadlessMode() {
   return headless;
 }
 
+bool IsAccessibleMode() {
+  bool accessible = GetConfigBool(false, kChromeFrameAccessibleMode);
+  return accessible;
+}
+
 bool IsUnpinnedMode() {
   // We only check this value once and then cache it since changing the registry
   // once we've pinned the DLL won't have any effect.