[Accessibility] Accessibility Digest, Vol 8, Issue 3

LUNEAU Fabrice fabrice.luneau76 at gmail.com
Thu Jan 29 17:32:15 CET 2015


Ok,  just a question..
To make sure that your inteface is fully accessible, do you turn off 
your display and use NVDA or Jaws ? ;P
I say it, when an another developpers say me that  work is accessible.
"Try again without screen"


Le 29/01/2015 16:26, verum nocte a écrit :
> Hi Fabrice!
>
> Yes. as you could read from previous mails Qt now supports 
> accessibility out of the box, no additional libraries or plugins 
> required. All one needs to do is set accessible names and descriptions 
> to widgets. Also, I tried using Qt creator with NVDA and to me (I am 
> not bind) it seems like it is fully accessible. Checkbox (including 
> text) is one of base widgets in qt and therefor accessible to readers 
> via its name and descriptions. Thanks for your input -  it is good 
> that other technologies support accessibly as well.
>
> Regards
>
> V
>
> On Mon, Jan 26, 2015 at 1:11 PM, LUNEAU Fabrice 
> <fabrice.luneau76 at gmail.com <mailto:fabrice.luneau76 at gmail.com>> wrote:
>
>     Hi everybody,
>
>     I am a french developper, and I am blind for 4 years.
>     I am following the list, even I don't use Qt anymore.
>     I learnt C/C++ at School and  I learnt just a little Qt after I got my
>     diploma.
>     Because I wanted to learn a C Gui API, and Microsoft api deguss me.
>     But 10 years ago, nobody known Qt.
>     So I have never praticed at work.
>
>     And now I work with Java/Swing and J2E.
>     I make accessibility for web and Swing, I am writting two articles on
>     this subject.
>     The good pratices are aviable to every API.
>     For example , define a tool tip text for component witch haven't text
>     (field,checkbox,...) because the labels located near are not read by
>     screen readers, but the tool tip text will be read.
>     Give the focus to the window and in the window give the focus  to
>     first
>     component  focusable.
>     There is  a Java accessibility  API, but I don't need  to use it, if I
>     respect simple rules.
>
>     I am not sure to  understand, why you need to make script.
>     Jaws and NVDA Script are  made to difficult case; when you have no
>     other
>     solutions.
>     Because it's very hard to maintain  them.
>     If the application is updated, sometimes you have to restart from
>     scratch.
>     Because it is not very scalable technology.
>
>     With Java ther are the java access bridge,  witch increase
>     accessibility.
>     you just need to set up it.
>     - windows key and u,
>     - use computer without display,
>     - check java access bridge check box.
>
>     Is Qt detect when a screen reader  is set up ?
>
>     Cordialement
>     Fabrice LUNEAU
>
>
>
>
>     Le 26/01/2015 12:00, accessibility-request at qt-project.org
>     <mailto:accessibility-request at qt-project.org> a écrit :
>     > Send Accessibility mailing list submissions to
>     > accessibility at qt-project.org <mailto: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
>     <mailto:accessibility-request at qt-project.org>
>     >
>     > You can reach the person managing the list at
>     > accessibility-owner at qt-project.org
>     <mailto: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. Re: basic accessibility in qt 5.4 (Andrei Tuicu)
>     >
>     >
>     >
>     ----------------------------------------------------------------------
>     >
>     > Message: 1
>     > Date: Sun, 25 Jan 2015 13:00:27 +0200
>     > From: Andrei Tuicu <andrei.tuicu at gmail.com
>     <mailto:andrei.tuicu at gmail.com>>
>     > Subject: Re: [Accessibility] basic accessibility in qt 5.4
>     > To: Steve Clarke <trumpton13 at trumpton.org.uk
>     <mailto:trumpton13 at trumpton.org.uk>>
>     > Cc: "accessibility at qt-project.org
>     <mailto:accessibility at qt-project.org>"
>     <accessibility at qt-project.org <mailto:accessibility at qt-project.org>>
>     > Message-ID:
>     >
>      <CAJb+n03a5om-48=V2DdG6APTgujWXyXds215oz5PGDgKxzjS=Q at mail.gmail.com
>     <mailto:Q at mail.gmail.com>>
>     > Content-Type: text/plain; charset="utf-8"
>     >
>     > Hello Steve!
>     >
>     > I have recently found out that JAWS is highly configurable using
>     Jaws
>     > Scripts. Qt applications will send the same information to any
>     assistive
>     > technology, but they might get filtered. From what I saw, NVDA is
>     > more talkative, but that's because JAWS filters more events. If
>     you want to
>     > see how an event is handled by Jaws (provided that you didn't
>     wrote a
>     > script yourself) check the DEFAULT.jss script and search for the
>     matching
>     > function. You can find the script by opening Utilities menu ->
>     Script
>     > Manager. I don't think it's recommended to make changes there,
>     but you can
>     > write a script for your own application to get the desired behavior.
>     >
>     > Have a nice day,
>     > Andrei
>     >
>     > 2015-01-25 12:28 GMT+02:00 Steve Clarke
>     <trumpton14 at trumpton.org.uk <mailto:trumpton14 at trumpton.org.uk>>:
>     >
>     >> I'm using 5.4.1, and I've not needed to #include
>     <Accessibility> - in fact,
>     >> now that accessibility is included in the qtbase, and not as a
>     plugin, all
>     >> I
>     >> need to do in qtcreator is set the accessible names.
>     >>
>     >> I develop apps on Linux using QTCreator, and I'm successfully
>     compiling
>     >> natively on a Windows PC with the freely available MSVC2010
>     compiler, on
>     >> the
>     >> command line.
>     >>
>     >> DIFFERENT SCREEN READERS
>     >>
>     >> Last year, I looked at different screen-readers and how
>     compatible they
>     >> were.
>     >> There's been lots of improvement, particularly with NVDA, but
>     Jaws and
>     >> Window
>     >> Eyes are woefully behind - mainly caused by the lack of support
>     / responses
>     >> from Jaws etc. themselves.
>     >>
>     >> DIFFERENT COMPILER BEHAVIOUR
>     >>
>     >> I would also point out that the compiler and the way you
>     compile have an
>     >> impact - last year, I had a go with cross-compiling with MinGW, and
>     >> couldn't
>     >> get accessibility to work at all.  Sniffing through the code
>     today, I see
>     >> an
>     >> example:
>     >>
>     >>
>     qtbase/src/plugins/platforms/windows/accessible/qwindowsaccessibility.cpp
>     >>    #ifdef Q_CC_MINGW
>     >>    # include "qwindowsmsaaaccessible.h"
>     >>    #else
>     >>    # include "iaccessible2.h"
>     >>    #endif
>     >>
>     >> Which would imply that MinGW and MSVC2010 may still provide
>     different
>     >> results.
>     >>
>     >> A USEFUL NVDA BRAILLE VIEWER TOOL
>     >>
>     >> I've been talking to the NVDA team, and have mentioned that it is
>     >> difficult to
>     >> check that an application correctly drives a braille display if
>     you don't
>     >> have
>     >> one to hand.  They responded quickly with a really small add-in
>     which puts
>     >> a
>     >> braille viewer on the screen (works fine on Windows 7, problems
>     with fonts
>     >> on
>     >> XP).
>     >>
>     >> The post can be found here:
>     >>
>     >> http://sourceforge.net/p/nvda/lists/message/33259006/
>     >>
>     >> And the BrailleViewer Add-In can be found here:
>     >>
>     >> https://dl.dropboxusercontent.com/u/28976681/brailleViewer.py?dl=1
>     >>
>     >> If you find it useful, I would encourange you to provide
>     feedback to the
>     >> NVDA
>     >> project, and they would consider putting it into the main
>     software release.
>     >>
>     >> Steve
>     >>
>     >> On Saturday 24 January 2015 14:21:03 verum nocte wrote:
>     >>> For further reference:
>     >>> To make basic accessibility one needs to:
>     >>>      -    #include <Accessibility> - (probably to .h file of
>     any class
>     >> with
>     >>> ui)
>     >>>      -    Write accessible names and accessible descriptions
>     (later is not
>     >>> necessary, but helps). This can be done ether through creator or
>     >>> grammatically.
>     >>>      -    Despite all (old) tutorials about deploying with
>     >>> qaccessbilewidgets4.dll and stuff one does not need to add
>     anything to
>     >>> achieve accessibility when dynamically linking on windows.
>     Currently
>     >>> (2015-01-24) my basic folder (that works) looks like:
>     >>>
>     >>>          application_folder
>     >>>              platforms
>     >>>                  qwindows.dll
>     >>>              application.exe
>     >>>              d3dcompiler_47.dll
>     >>>              icudt53.dll
>     >>>              icuin53.dll
>     >>>              icuuc53.dll
>     >>>              libEGL.dll
>     >>>              libGLESv2.dll
>     >>>              msvcp120.dll
>     >>>              msvcr120.dll
>     >>>              Qt5Core.dll
>     >>>              Qt5Gui.dll
>     >>>              Qt5Widgets.dll
>     >>>
>     >>> All the dll's exept for msvcp120.dll and msvcr120 are (for me)
>     available
>     >> in
>     >>> Qt/5.4/msvc2013_64. Of course to achieve additional
>     functionalities one
>     >>> would need more than that, but just to work with nvda that is
>     all one
>     >>> needs. Awesome. It was too easy :):
>     >> _______________________________________________
>     >> Accessibility mailing list
>     >> Accessibility at qt-project.org <mailto:Accessibility at qt-project.org>
>     >> http://lists.qt-project.org/mailman/listinfo/accessibility
>     >>
>     > -------------- next part --------------
>     > An HTML attachment was scrubbed...
>     > URL:
>     http://lists.qt-project.org/pipermail/accessibility/attachments/20150125/4886e6e9/attachment-0001.html
>     >
>     > ------------------------------
>     >
>     > _______________________________________________
>     > Accessibility mailing list
>     > Accessibility at qt-project.org <mailto:Accessibility at qt-project.org>
>     > http://lists.qt-project.org/mailman/listinfo/accessibility
>     >
>     >
>     > End of Accessibility Digest, Vol 8, Issue 3
>     > *******************************************
>
>
>     _______________________________________________
>     Accessibility mailing list
>     Accessibility at qt-project.org <mailto:Accessibility at qt-project.org>
>     http://lists.qt-project.org/mailman/listinfo/accessibility
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/accessibility/attachments/20150129/02e8f7cb/attachment.html>


More information about the Accessibility mailing list