[tbb-bugs] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:
                                                 |  pospeselr
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  High                                 |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,      |  Actual Points:
  TorBrowserTeam201903, GeorgKoppen201903,       |
  tbb-8.5-must                                   |
Parent ID:                                       |         Points:
 Reviewer:  boklm                                |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by pospeselr):

 Replying to [comment:54 onionsoup]:
 > Replying to [comment:53 pospeselr]:
 > > Replying to [comment:52 gk]:
 > > > That's interesting. Care to share a 32bit bundle so others affected
 in this bug can test/verify that assumption?
 > >
 > > I had bundle baking over night and it has the same (correct) behaviour
 as my hacked together one:
 > >
 > > 32-bit: https://people.torproject.org/~richard/builds/torbrowser-
 nightly_en-US-i686-27503.exe
 > > 64-bit: *later today*
 >
 > I just ran the 32 bit test bundle. When I load pages now, NVDA doesn't
 seem to treat them as a web page, though it is able to tab around to
 links, form controls and such. I am, however, unable to switch to browse
 mode to interact with the document like a webpage (I tried pressing
 NVDA+space, nothing happened). To see what NVDA should be doing, try going
 into Firefox or Chrome, and navigate by element, such as to next heading
 (press h) or read the webpage with arrow keys. I suspect that the fix is
 simple, as NVDA definitely sees the rendered content, it just doesn't seem
 to treat it as a web document.
 > Hopefully I make sense - I'm not very well-versed in terminology.

 Sorry, didn't know NVDA could do that. So what I see (on 32-bit Windows 10
 with 32-bit Tor Browser) is that NVDA now reads out web content when it's
 moused-over (where as before it did not).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27503#comment:55>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online