<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Wait... is it really confirmed that Narrator can't work with
(hardened) VirtualBox either? That would mean our devs must have
been testing the wrong thing for quite a while now. It certainly
hasn't reached my attention so far.<br>
<br>
For many reasons we cannot recommend that random people run
non-hardened builds. What might be a way out (not with the current
builds, they would be affected by hardening) is to ship an
additional compilation of the VM UI which is not subject to
hardening and can be used solely with the "separate VM/UI process"
option which VirtualBox has already. Would bring some minor feature
losses, but if that would bring back full accessibility I can see a
good justification for spending the necessary time.<br>
<br>
Klaus<br>
<br>
<div class="moz-cite-prefix">On 25.09.2018 19:26, Mihai Hanor wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALv6pCZR-NEhoR4Mt6p9L3bnLqp9yJMetf-H7=0JVGrWHy-VQg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">Hello,
<div><br>
</div>
<div>I'm not a developer, but I have some experience with
VirtualBox. The reason why not even Microsoft's narrator is
able to work with VirtualBox is the hardening of the
VirtualBox process, which is enforced to protect the VM from
eavesdropping (I think). You can look at the VirtualBox SDK,
but you'll probably not find what you're looking for. Also,
integrating the NVDA client controller is probably not going
to happen and it doesn't look useful, because it requires
VirtualBox to send stuff to NVDA (by looking at the C
example), which would require considerable effort to rewrite
the GUI. The most achievable task might be to build VirtualBox
OSE for Windows, without hardening. A much harder task would
be to separate the the frontend/GUI part from the VM process
and make the frontend run in a normal process. In the upcoming
major release of VirtualBox, it looks like the devs have made
a move to separate the VM process, but I'm don't know to what
end. The frontend still runs in a hardened process.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mihai Hanor</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Sep 21, 2018 at 12:30 PM Илья Пащук <<a
href="mailto:ilusha.paschuk@gmail.com" target="_blank"
moz-do-not-send="true">ilusha.paschuk@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">helo.<br>
<br>
<br>
I'm a nvda (<a href="http://nvaccess.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">nvaccess.org</a>)
screenreader addon developer<br>
<br>
I need the way to get some object text in vbox gui, that
unaccessable by <br>
standard methods.<br>
<br>
are there any api interface to get this info from vbox gui?<br>
<br>
<br>
i'm using python.<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>