GNOME.org
 

Re: [orca-list] Qt 5 accessibility

Hello,
I am sorry my attempt at some kind of report was not something you would consider as a polite request. Anyway is there a way for you or someone else close enough on the team to at least do some verry basic testing with the real screen reader orca on linux in this specific case please? Also would you like me to write reports in a way so you will get steps to reproduce, current behaviour and expected behaviour? This is something I believe I can do and if it may eventually help to make QT accessibility become even better in the future, then I am happy to do that. I haven't tested QT5 on windows so I can't comment on this right now but I can remember having issues for example with tabcontrols on all the platforms in the past so I've assumed most of these critical issues target multiplatforms where possible. 

Thanks and greetings

Peter


On 02.06.2014 13:57, Frederik Gladhorn wrote:

Hi,

Peter, thanks for your feedback. In the last three months we closed 44
accessibility issues in Qt, of course not all of them will end up in a release
right away. Also I personally worked on a lot of Mac and Windows issues since
I got high quality bug reports on these platforms.

This is the first time I get any feedback when it comes to accessibility on
Linux with Qt 5.3, so I am not surprised that there are issues. Please let me
know when you run into problems.

On Friday, May 30, 2014 12:00:26 PM Peter Vágner wrote:

Hello,
I have briefly tested transmission-qt with QT 5.3 on arch linux today.
I am not happy to report that:
- comboboxes

I wonder if the problem you are seeing is this bug:
https://bugreports.qt-project.org/browse/QTBUG-36814
(fixed in 5.3.1)


, sliders appear to be still broken ei.e. not correctly
firing value change events.

Can you please give more details? I just tested a simple Qt example that ships
with Qt (widgets/sliders) and for me sliders work (Orca announces the new
value after pressing the arrow keys.
Funny enough sliders and dial don't do that.
https://bugreports.qt-project.org/browse/QTBUG-39394


I am having issues navigating in edit fields (note this appears to be
working better with QT4).

Please give more details. Ideally a bug report at https://bugreports.qt-project.org
(the account creation currently has a visual only captcha, sorry for that.
Upgrading the bug tracker is scheduled but non-trivial, but you can send a
mail to jira-admin qt-project org and will get an account).


Perhaps there are under the hoodstability and other fixes but I am
afraid real accessibility testing by the potential users is either not
taken into considerations while working on this or it's being put aside
for the consideration to the future updates.

We test as much as we can, but not depending on a screen reader it's sometimes
hard to tell what is working and what isn't. So please give feedback,
otherwise I cannot spend time on this.

Greetings,
Frederik


Other things which I can't say are QT5 issues or might be app specific
issues is that flat review does not work and some of the controls don't
convey its role and state.
I have studied no implementation details I have observed all this by
running orca and my guess work as I can't see at all.

I am looking forward to some real exciting developments on this front.

Greetings

Peter

On 20.05.2014 15:35, Frederik Gladhorn wrote:

Hello,

since Qt accessibility comes up as a topic every once in a while, I
thought
I'd give a short update.

Qt 5 is looking better and better when it comes to accessibility. Today Qt
5.3.0 was released and the release contains quite some improvements across
the board and on all platforms. I recently wrote a blog post about it:
http://blog.qt.digia.com/blog/2014/05/14/accessibility-in-qt-5-3/

Since KDE is slowly moving towards a release based on Qt 5, I hope that
we'll be able to provide a decent experience for everyone from the
release of Plasma Next and onwards. By the way, the old environment
variable to enable accessibility has been retired and Qt now ships and
builds all accessibility code by default, not depending on external
plugins any more.

I'd also like to mention that we now have a dedicated mailing list to
discuss Qt accessibility issues:
http://lists.qt-project.org/mailman/listinfo/accessibility

Another nice project that just started is a cooperation to improve
accessibility for Qt apps on mobile devices (targeting Android and iOS).

Let me quote Trenton:

My name is Trenton Schulz. I’m a senior research scientist at the
Norwegian
Computing Center (Norsk Regnesentral), and I’m working with Digia on our
BestApps project [1] for increasing the accessibility of mobile apps.

Currently, we are doing some user investigation about how different
people
use assistive technology (AT) with their smartphones and apps. In
connection with this, I would be interested in finding people that would
be
interested in participating in a small interview (either over telephone,
Skype, or email) about how they use this technology. We are holding a
workshop connected to this as well on 19 June in Oslo.

So, if you are interested (or know anyone), please let me know via email
and I can send more details. Your input can help make future Qt
applications more accessible and easier to use for everyone.

I'm looking forward to feedback from the Orca users as more Qt 5
applications become available on Linux.

Greetings,
Frederik

PS: Qt 4 is in maintenance mode and there will be no real changes in
accessibility for it.

_______________________________________________
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
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]