Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, on Fri 11 Dec 2015 18:11:40 -0300, wrote:
> Ah, now I get it. Please go ahead.

Good, now done!

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Lisandro Damián Nicanor Pérez Meyer]

Ah, now I get it. Please go ahead.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, on Wed 09 Dec 2015 22:27:51 -0300, wrote:
> On Tuesday 08 December 2015 20:28:29 Samuel Thibault wrote:
> [snip] 
> > So, how is it going?  Can we proceeed?
> 
> I pushed the necessary changes to qt4 on Nov 17th, qt4-x11 (4:4.8.7+dfsg-4). 
> If I'm missing something please do not heasitate in replying :)

The additional dependency is useful to make sure that the bridge is
there, but it is not activated by default, i.e. one can not just start
the screen reader to get access to already-running applications.  We
need to set QT_ACCESSIBILITY to 1 for that, which will enable some parts
of qt-at-spi so that the screen reader can access already-running
applications.  I planned to do that in the at-spi2-core package once Qt
people tell me it's OK to do it.

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 08 December 2015 20:28:29 Samuel Thibault wrote:
[snip] 
> So, how is it going?  Can we proceeed?

I pushed the necessary changes to qt4 on Nov 17th, qt4-x11 (4:4.8.7+dfsg-4). 
If I'm missing something please do not heasitate in replying :)


-- 
http://mx.grulic.org.ar/lurker/message/20081108.174208.4f42e55c.es.html
Así se corrobora el software legal en Argentina

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, on Tue 01 Sep 2015 18:50:43 -0300, wrote:
> On Tuesday 01 September 2015 01:39:51 Samuel Thibault wrote:
> > As discussed at DebConf [1,2,3], we would like to make the accessibility
> > stack enabled by default, so that all a user who needs it has to do is
> > just to start orca

> > Considering that we
> > are just at the beginning of the Stretch development, perhaps we can
> > try to enable accessibility by default in both Qt4 and Qt5, see how
> > well this goes, and at worse not enable it by default for Qt4 if the
> > possibly-revealed bugs become really not solvable?
> 
> I like the idea, but ~1 month after the gcc5 transition ends. We are also 
> pushing KDE+Qt5 to the archive and have quite some problems with the 
> transition, so it would be better to let the transition "dust" settle down 
> before adding yet more sources of bugs. After that we should definitely give 
> it a try IMO.

So, how is it going?  Can we proceeed?

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Mario Lang]

Samuel Thibault  writes:

> Lisandro Damián Nicanor Pérez Meyer, le Tue 01 Sep 2015 18:50:43 -0300, a 
> écrit :
>> Now we should also consider Wayland and even pure console. Qt5 has been 
>> improving in this side (yes, it can draw a GUI without X and without the 
>> need 
>> to recompile anything). I don't know if a11y is present in those cases, but 
>> if 
>> it is it would also be good to check them.
>
> AT-SPI is actually independent from the actual rendering, so it should
> be already working.

If we are talking about Qt on framebuffers (how cool!), I doubt that it
would be practical to use if it already "worked".  After all, Orca would
still need to run in a conventional X session, wouldn't it?  And d-bus
would need to be convinced to have those two talk to each other.
And then, all of the orca keyboard based commands would likely no longer
work, because the current console would be the wrong on.  Or am I
misunderstanding anything here?

Still, this would be very cool to have working.  What do I need to do,
to let a Qt5 app know it is supposed to do this?

-- 
CYa,
  ⡍⠁⠗⠊⠕


signature.asc
Description: PGP signature

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

BTW, we'd like to enable speech synthesis by default when speech was
used during installation. AIUI, it is a matter of running this

qdbus org.kde.kaccessibleapp /Adaptor setSpeechEnabled true

but during installation we don't have an X session, and dbus tells me

Error: org.freedesktop.DBus.Error.NoReply
Message did not receive a reply (timeout by message bus)

In the gconf/gsettings case we could go around this kind of issue by
rather leaving a schema file in an appropriate place. Is there this kind
of possibility with kdbus?

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, le Tue 01 Sep 2015 18:50:43 -0300, a écrit 
:
> On Tuesday 01 September 2015 01:39:51 Samuel Thibault wrote:
> > For Qt4, this is implemented in the qt-at-spi package, which has been
> > developped mostly between 2009 and 2013.  There doesn't seem to be much
> > activity there since early 2013.
> 
> Kind of. See the last part of the first message in:
> 
> 

I remember this well ;)

> And the following comments. I'll try to get at it as soon as possible, but 
> not 
> before the gcc5 transition ends.

Sure.

> Now we should also consider Wayland and even pure console. Qt5 has been 
> improving in this side (yes, it can draw a GUI without X and without the need 
> to recompile anything). I don't know if a11y is present in those cases, but 
> if 
> it is it would also be good to check them.

AT-SPI is actually independent from the actual rendering, so it should
be already working.

Samuel