Re: [orca-list] [Kde-accessibility] Ubuntu Unity Desktop to go to Mir and QT

[Alex Midence <alex midence gmail com>]

I'll create a virtual machine and begin testing before the month is up.  Do
I need to have something like Fedora Rawhide or Ubuntu 13.10 to test in an
environment that will give you valuable data?  

Alex M


-----Original Message-----
From: Frederik Gladhorn [mailto:frederik gladhorn de] 
Sent: Wednesday, July 24, 2013 10:35 AM
To: kde-accessibility kde org; 'Ubuntu Accessibility Mailing List';
orca-list gnome org
Cc: Alex Midence; 'Krishnakant Mane'
Subject: Re: [orca-list] [Kde-accessibility] Ubuntu Unity Desktop to go to
Mir and QT

Onsdag 24. juli 2013 08.47.34 skrev Alex Midence:
> Very true.  The thing that I want to test is editable text areas in QT.
> That was the biggest problem I saw last year when I was trying out 
> KDE.  If you were in Kate or Kmail and there was some text you wanted 
> to put in either because you were editing a file or filling out a form 
> of some kind, Orca couldn't read it back to you.  If it was a field 
> you were filling in, you could tab away and backtab back to it and 
> Orca would speak its contents but, individual character by character 
> or word by word navigation was not possible at the time.  I hope 
> that's gotten better since then.  I haven't looked at it since May or 
> June of last year, I think.  It is a very important piece of the puzzle.

For Kate it would be great if I could get bug reports with an easy
description on https://bugs.kde.org .

Another interesting thing to try would be Qt Creator - which is probably
quite complex to test, but for me the editor pretty much works with Orca. Or
as a simpler test the text editor example that is shipped with Qt 5
(examples/widgets/richtext/textedit). In general using one of the many
examples shipped with Qt makes it easier for me to reproduce bugs, feel free
to file Qt accessibility bugs on https://bugreports.qt-project.org and make
sure to choose "Gui: Accessibility" as component.

Generally the text interfaces should be much better in Qt 5 compared to Qt
4, but need some testing.

KMail is using WebKit and is not expected to work all that great (even
though Jose made it work much better than before).

Greetings
Frederik

> Alex M
>
>
>
> From: Krishnakant Mane [mailto:krmane gmail com]
> Sent: Wednesday, July 24, 2013 8:42 AM
> To: Alex Midence
> Cc: 'Frederik Gladhorn'; kde-accessibility kde org; 
> vinux-support googlegroups com; 'Ubuntu Accessibility Mailing List'; 
> orca-list gnome org
> Subject: Re: [orca-list] [Kde-accessibility] Ubuntu Unity Desktop to 
> go to Mir and QT
>
>
>
> This essentially means we must try things pretty early on and start 
> reporting bugs agressively.
> happy hacking.
> Krishnakant.
>
> On 07/24/2013 06:37 PM, Alex Midence wrote:
>
> Wonderful news!  I certainly feel better for it.  Thanks for all your 
> hard work on qt-at-spi.
>
>
>
> Alex M
>
>
>
>
>
> From: Frederik Gladhorn [mailto:frederik gladhorn de]
> Sent: Wednesday, July 24, 2013 3:21 AM
> To: kde-accessibility kde org
> Cc: Alex Midence; orca-list gnome org; vinux-support googlegroups com; 
> Ubuntu Accessibility Mailing List
> Subject: Re: [Kde-accessibility] Ubuntu Unity Desktop to go to Mir and 
> QT
>
>
>
> Hello,
>
>
>
> On Tuesday 23. July 2013 13.23.47 Alex Midence wrote:
>
>
> Hi, all,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> It looks like Ubuntu's Unity desktop will be switching to QT/QML in 
> the
>
> near
>
>
> future. It looks like they'll be using QT5. Does anyone know the 
> current
>
>
>
> state of accessibility for qt5 or QML? We were all disappointed to 
> find
>
>
>
> out that Unity 2d was discontinued in Ubuntu 12.04 and it is believed 
> that
>
>
>
> Ubuntu 14.04 would continue it's wonderfully accessible legacy. This 
> was
>
>
>
> supposed to soothe our ruffled feathers when 12.10 and 13.04 came out 
> with
>
>
>
> Unity 3d only which was not as accessible. Well, now, I am curious to 
> know
>
>
>
> if the timetable for that level of accessibility in a Ubuntu desktop 
> will
>
>
>
> need to be pushed back even more in light of this development. Please 
> see
>
>
>
> link below:
>
>
>
>
>
>
>
>
> Qt 5 contains all the accessibility code that was used for Qt 4, 
> including the plugin qt-at-spi which will then no longer be needed. 
> Many things have also been improved since we learned from finally making
Qt 4 accessible.
> All in all this means that the Qt 5 based Unity should be able to 
> reach the level of the old Unity and hopefully exceed it. Of course 
> that's still up to the Unity developers and probably a fix here or 
> there in Qt, but generally I would expect things to look good.
>
>
>
> Greetings
>
> Frederik
>
>
>
>
>
>
>
>
>
>
>
>
> http://www.omgubuntu.co.uk/2013/03/unity-next-project-announced
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> Alex M
>
>
>
>
>
>
>
>
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at
> http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org Find out 
> how to help at http://live.gnome.org/Orca/HowCanIHelp