- Electron version: 0.37.6
- Operating system: Windows 10

In VSCode, in order to support screen readers while editing text, we set the contents of a `<textarea>` to the contents of the line and lines surrounding the cursor and we mirror the editor selection in the `<textarea>` via `setSelectionRange`.

Chromium is not the fastest when it comes to setting large amounts of text :) (such as > 10,000 characters) and basically stalls all the time. Apparently, Electron already has some knowledge about when a screen reader is attached to the main process window (in C++ code). Is it possible to expose this as a getter + event when it first happens in the `electron` API.

We could then maintain this costly `<textarea>` sync only when really needed.

atom/browser/native_window_views_win.cc
}
}  
bool NativeWindowViews::ExecuteWindowsCommand(int command_id) {
  std::string command = AppCommandToString(command_id);
  NotifyWindowExecuteWindowsCommand(command);
  return false;
}
bool NativeWindowViews::PreHandleMSG(
    UINT message, WPARAM w_param, LPARAM l_param, LRESULT* result) {
  NotifyWindowMessage(message, w_param, l_param);
  switch (message) {
    
    
    
    
    
    case WM_GETOBJECT: {
      const DWORD obj_id = static_cast<DWORD>(l_param);
      if (enabled_a11y_support_) return false;
      if (obj_id == OBJID_CLIENT) {
        const auto axState = content::BrowserAccessibilityState::GetInstance();
        if (axState && !axState->IsAccessibleBrowser()) {
          axState->OnScreenReaderDetected();
          enabled_a11y_support_ = true;
        }
      }
      return false;
    }
    case WM_COMMAND: