On 02/05/2019 01:52, rjai...@gmail.com wrote:
I was helping a blind ham set up WSJT-X 2.1.0-rc5 today and it was
apparent that this new arrangement to thwart robots simply isn't
working for blind hams who rely upon screen readers and other
accessibility technologies. There is no way for his screen reader
software to focus on OK.
Any help with this would be appreciated.
73
Ria, N2RJ
Hi Ria,
sorry to here that, an unfortunate consequence of a few LIDs making
things worse for the good guys. As the community appears to have no
interest in stopping them from destroying the WSJT-X modes for everyone
who is adopting them, we are in a tough place. We could easily
distribute a version of WSJT-X with these defences disabled for those
that ask for it. All this noise in the defence of sight-challenged
operators seems selfish to me, yours is the first that actually mentions
someone having difficulty. We use tools that automatically build in
accessibility on all platforms, we work with other software developers
who are developing special tools for sight-challenged ops (e.g. Sam,
W2JDB, with his application Qlog). Yet when we have to make a change to
one pair of buttons within the hundreds of controls in WSJT-X, for
reasons we don't like either but we think they are justified, we are
branded as anti-accessibility.
Come on folks, try and see the big picture.
Ria, which operating system is your colleague using? Also what screen
reader is their preference, if it is free of charge or otherwise easy to
obtain I would like to review how WSJT-X plays out when accessing the
programmatic accessible interfaces. I ask because we could do a lot more
with the accessible names and descriptions of the various windows and
controls in WSJT-X. They are largely at default values presently which
can't be very helpful.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
