[Accessibility] Accessibility Digest, Vol 9, Issue 5

Wed Feb 18 11:46:02 CET 2015

Bonjour,

As I say previoulsy I am blind french devellopper, but in Java/J2E.
I follow the list because I plan to use Qt to test accissibility level.
However I have experience to make accessibility with Swing and other GUI

The following tip work in many cases.

In first time a label is not focusable, so Jaws or NVDA  will not able 
to read it.
A label describe an other element a field for example.
Try to find a function to join the element and the label(setLabelFor)
Or you can set up a tool tip text, for the conponent,  it works to
The last solution îs using a lield with a text, but in disabled mode.

In a second time you should give the the focus to the main window and 
after to the the first conponent focussable that yoyr user will use 
first in your application

Jaws key + b read the window as a text

Cordialement
Fabrice

A
Le 17/02/2015 12:00, accessibility-request at qt-project.org a écrit :
> Send Accessibility mailing list submissions to
> 	accessibility at qt-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.qt-project.org/mailman/listinfo/accessibility
> or, via email, send a message with subject or body 'help' to
> 	accessibility-request at qt-project.org
>
> You can reach the person managing the list at
> 	accessibility-owner at qt-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Accessibility digest..."
>
>
> Today's Topics:
>
>     1. QLabels not read by JAWS screenreader (Qt 5.4/Win	8.1) (Marcel)
>     2. Re: How do you run QT / QT Apps with a Screen	Reader and
>        Valgrind (Frederik Gladhorn)
>     3. Re: QLabels not read by JAWS screenreader (Qt	5.4/Win 8.1)
>        (Frederik Gladhorn)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 16 Feb 2015 17:51:30 +0100
> From: Marcel <lists at nightsoul.org>
> Subject: [Accessibility] QLabels not read by JAWS screenreader (Qt
> 	5.4/Win	8.1)
> To: accessibility at qt-project.org
> Message-ID: <C2EAF4E4-3AC7-4BBB-A1D8-5C8E333F0735 at nightsoul.org>
> Content-Type: text/plain; charset=utf-8
>
> [Crosspost from the qt-project.org forums, didn?t receive a reply there within a week.]
>
> Hello!
>
> I?m trying to make our application accessible with a screenreader. A blind colleague uses JAWS, therefore I use that for testing. Reading widgets that expect user input works quite well so far, but I?m having some trouble elsewhere:
>
> QLabels are not read at all. JAWS has a hotkey that should ?read the whole window? (JAWS-Key + B), but for our application that just reads the window title and nothing else. Everything I can focus directly via tabbing is read as well ? which is of course not desirable with labels.
>
> Probably related: We have some QWizards set up. There, the QWizardPage title and description texts are used to convey most of the information concerning the wizard page?s purpose. Those texts are not read at all as well.
>
> I have a minimal test case application[0] that has a label (not read), a button and a QLineEdit (accessibleName read fine for both). The button opens a wizard that has title and description (not read) and no further input widgets.
>
> Do accessible applications usually have all necessary information in input widget descriptions (therefore not needing labels) or am I doing something wrong?
>
> This is Qt 5.4 on Windows 8.1 with JAWS 16.
>
> Greetings,
> Marcel
>
> [0] https://filetrain.de/a11ytest.zip
>
> ------------------------------
>
> Message: 2
> Date: Tue, 17 Feb 2015 11:18:16 +0100
> From: Frederik Gladhorn <frederik.gladhorn at theqtcompany.com>
> Subject: Re: [Accessibility] How do you run QT / QT Apps with a Screen
> 	Reader and Valgrind
> To: <accessibility at qt-project.org>
> Message-ID: <27938330.7ka4KFz524 at frederik-thinkcentre-m93p>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Steve,
>
> On Sunday, February 15, 2015 09:49:10 AM Steve C wrote:
>> In digging around within QT, I've stumbled across a lock-up scenario that
>> only exhibits itself when NVDA is running (bug reported).  Stepping through
>> the code, it looks like a response to a get attributes is being corrupted,
>> and looking at the code, I can't see where / how - in fact, if I step
>> through the code, it doesn't get corrupted!
> Debuggers interfere with the program run, for example when a pointer is not 0-
> initialized, you may get invalid data, but debuggers often set memory to 0.
>
>> I'm imagining that it is caused by a memory leak elsewhere.
> Leaks show as increased memory consumption, not crashes.
>> As far as I can read, valgrind and windows don't work together, and wine and
>> NVDA don't work together.
> No, I don't think this would work, running wine in valgrind won't work.
>> My quesiton is: has anyone tried running a memory analyser with QT running
>> alongside a windows screen reader?  if so, how?
> I think all Windows memory analysis tools are expensive, so either you invest,
> or you fall back to some other means of debugging. If you know the call that
> triggers it reproducibly, then you can fall back to printf/qDebug debugging
> without a debugger and narrow down where the crash happens.
>
> Cheers,
> Frederik
>
>> Thanks and Regards,
>>
>> Steve
>>
>> _______________________________________________
>> Accessibility mailing list
>> Accessibility at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/accessibility
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 17 Feb 2015 11:23:53 +0100
> From: Frederik Gladhorn <frederik.gladhorn at theqtcompany.com>
> Subject: Re: [Accessibility] QLabels not read by JAWS screenreader (Qt
> 	5.4/Win 8.1)
> To: <accessibility at qt-project.org>
> Message-ID: <2464698.ysFQrH11qW at frederik-thinkcentre-m93p>
> Content-Type: text/plain; charset="utf-8"
>
> On Monday, February 16, 2015 05:51:30 PM Marcel wrote:
>> [Crosspost from the qt-project.org forums, didn?t receive a reply there
>> within a week.]
>>
>> Hello!
>>
>> I?m trying to make our application accessible with a screenreader. A blind
>> colleague uses JAWS, therefore I use that for testing. Reading widgets that
>> expect user input works quite well so far, but I?m having some trouble
>> elsewhere:
>>
>> QLabels are not read at all. JAWS has a hotkey that should ?read the whole
>> window? (JAWS-Key + B), but for our application that just reads the window
>> title and nothing else. Everything I can focus directly via tabbing is read
>> as well ? which is of course not desirable with labels.
>>
>> Probably related: We have some QWizards set up. There, the QWizardPage title
>> and description texts are used to convey most of the information concerning
>> the wizard page?s purpose. Those texts are not read at all as well.
>>
>> I have a minimal test case application[0] that has a label (not read), a
>> button and a QLineEdit (accessibleName read fine for both). The button
>> opens a wizard that has title and description (not read) and no further
>> input widgets.
>>
>> Do accessible applications usually have all necessary information in input
>> widget descriptions (therefore not needing labels) or am I doing something
>> wrong?
>>
>> This is Qt 5.4 on Windows 8.1 with JAWS 16.
> QLabel should provide accessibility information (it is represented by
> QAccessibleDisplay in qtbase/src/widgets/accessible/simplewidgets.h).
>
> It would be interesting to know if it works with NVDA (I suspect that it does,
> looking at Steve's testing. The issue seems to be that we expose the
> information in a way that JAWS either ignores it or doesn't see it at all, so
> it's a bug in Qt.
>
> It would be great if you file a bug report (https://bugreports.qt.io) so we
> keep track of it.
>
> Does anyone know if JAWS makes use of IAccessible2 at all? Maybe that is the
> reason for it not working.
>
> Cheers,
> Frederik
>
>> Greetings,
>> Marcel
>>
>> [0] https://filetrain.de/a11ytest.zip
>> _______________________________________________
>> Accessibility mailing list
>> Accessibility at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/accessibility
>
>
> ------------------------------
>
> _______________________________________________
> Accessibility mailing list
> Accessibility at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/accessibility
>
>
> End of Accessibility Digest, Vol 9, Issue 5
> *******************************************