[Accessibility] Accessibility Digest, Vol 8, Issue 6

LUNEAU Fabrice fabrice.luneau76 at gmail.com
Thu Feb 5 16:55:05 CET 2015


Yes, in fact Many developers don't have a braille display, .
But many blind to, it s very expensive 4000€ for a typycal personnal  { 
We count that it costs 100 €  for each cells.
But you don't need a braille display,  to test accessibility.
Personnaly I yse very few the mine.
There are some mad blinds, who use only braille display, with linux on 
text mode.

About software you can use Jaws for free during 45 minutes sessions
It is enough for testing, your work.
And after you just need to restart.
There are some problems with Windows 8.1, which  is never realy stoped.
I have never used windows eye, in France the blind learn Jaws and NVDA 
at school.
I have no idea aabout other countries, but  Jaws and  Zoom Text seems 
the most used software by visual defficient in the world.

Le 30/01/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. Re: Accessibility Digest, Vol 8, Issue 3 (Steve C)
> ----------------------------------------------------------------------
> Message: 1
> Date: Thu, 29 Jan 2015 18:03:53 +0000
> From: Steve C <list15 at trumpton.org.uk>
> Subject: Re: [Accessibility] Accessibility Digest, Vol 8, Issue 3
> To: accessibility at qt-project.org
> Message-ID: <6442489.xRWF4c9HTQ at dime>
> Content-Type: text/plain; charset="us-ascii"
> On Thursday 29 January 2015 17:32:15 LUNEAU Fabrice wrote:
>> 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"
> I would recommend installing a screen-reader - you need to be aware that the
> voice and braille outputs are not driven from the same information source, and
> there can be scenarios (usually bugs) where one works and the other one
> doesn't - so it is good to check both.
> Many developers don't have a braille display, but most screen-readers have an
> emulator as a bolt-on.  Jaws and Windows Eyes have this feature, but will only
> run for a month, then for 20 minutes or so without a reboot (licensing).
> NVDA is free, and there is a python add-in you can use to display what would
> be on a braille display.  Note that NVDA displays the actual braille, whereas
> Jaws and WIndows Eyes show the text as normal characters.
> Note also that if you want you application to work with all screen-readers,
> you need to test it with more than one.  NVDA is by far the best supported, so
> I'd start with that one.
> Steve
> For the NVDA Braille Vierwe, Copy ...
> https://dl.dropboxusercontent.com/u/28976681/brailleViewer.py?dl=1
>   ... into brailleDisplayDrivers directory inside the user
> configuration directory; e.g. %appdata%\nvda\brailleDisplayDrivers
> ------------------------------
> _______________________________________________
> Accessibility mailing list
> Accessibility at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/accessibility
> End of Accessibility Digest, Vol 8, Issue 6
> *******************************************

More information about the Accessibility mailing list