Branching from parent bug 825698, but not blocking.

Note: These are Windows-only and also lower-priority than 915837, but should still be fixed.

//// 
Windows 10
JAWS 2019.1810.64 ILM
NVDA 2018.3.1 
Chrome 72.0.3599.0 (Official Build) canary (32-bit) (cohort:Clang-32)
flag set to enabled: #omnibox-drive-suggestions
Signed in with google.com address

1. Enable the setting itself per the steps listed above - FAIL with JAWS, FAIL with NVDA 

 Bug A (not a blocker since it's the screen reader's fault): JAWS 2019 does not read the text associated with the button at all, nor does it even say that it is a button. Upon putting focus on it, JAWS only says "Pressed". However, if you then press the space bar or activate the control back and forth, it reads "Google Drive search suggestions" and the state of the button correctly. It only happens when you put focus on the control the first time. 
However, since JAWS 2018 works without issue, this can be ignored as part of this review and I'll open the bug with the manufacturer. 


 Bug B (not a blocker, should be fixed): With NVDA, the text "Chrome will access your Drive..." is read as clickable even though clicking it only toggles the switch. This is not correct, it shouldn't be labeled clickable. 

 Bug C (not a blocker, should be fixed): With NVDA, after toggling the toggle button on or off, NVDA does not announce the text associated with that button. It simply says "Pressed" or "Not pressed" instead of "Pressed Google Drive search suggestions"