CIRCLE WITH A DOT

@kaveinthran @NVAccess @jcsteh @stevenscott @joslee I am low vision myself, and as someone who uses the built-in Windows Magnifier in combination with NVDA, my biggest concern about having a built-in Magnifier, especially enabled by default, aside from the obvious fact of conflicts, is the single point of failure. The Windows Magnifier is lightweight and reliable, to the point where it doesn't crash even on the most basic system. My main concern here is that if this becomes a standard feature of NVDA, and NVDA crashes, you simultaneously lose your speech and your magnification in the event of a complete NVDA lock up. I personally would either give the option to not have it on by default, or make the screen magnifier a separate project (like how Fusion is separate from JAWS). Moreover, my other concern relates to keyboard shortcut hotkeys, as if NV Access decides for some reason that it should prioritize its Magnifier over the Windows one as a Magnifier user, I don't consider that a wise choice, especially if the Windows Magnifier does the job flawlessly. I'd consider the feature redundant and having it run under a single process I fear will add massive overhead from a performance perspective. This isn't Windows 7 anymore, where Magnifier's full screen feature relied on Aero to the point where not having it on meant you were stuck with the infamous docked mode from Windows Vista and earlier. This was one of my issues with using JAWS in Windows 7 that prompted me to switch to NVDA back in the day, mainly because JAWS would disable DWM, turning on Windows 7 Basic, thus killing Aero and the full screen magnification feature with it. As of Windows 8 and later, DWM is no longer a requirement for the full screen magnification feature built into Windows, so I do have to ask, is there really any advantages to having the Magnifier tool built into NVDA when a quick, easy Magnifier is ready to launch?