Apart from ADA stuff it simply isn't working for blind hams. Besides, the autobots have gotten advanced now to the point where they are simply modifying source code and bypassing all manual input.
Not sure what can be done other than maybe invalidate awards from automated robot cheating. Ria N2RJ On Wed, 1 May 2019 at 14:22, Mark James <markhjame...@gmail.com> wrote: > Note: I think this post is appropriate on this list because it involves an > important software development issue. > > I'm not going to comment on the details of the interface, but I think it > is worth pointing out that a software interface that requires using a mouse > to click a button is in violation of the US Americans with Disabilities > Act. Under the ADA you must provide a keyboard option. > > While a free, open-source program might not face any specific penalty > here, but not being ADA-compliant at least in theory could result in the > software not being allowed to be used in schools, colleges, or any public > institution. > > Besides, being ADA complaint is just the right thing to do. > > Frankly I think any attempt to make it harder to use macros will result in > flunking the accessibility goal. > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-883129225528624055_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Wed, May 1, 2019 at 12:22 AM Aaron Jones <aa...@ag7gk.org> wrote: > >> Dev Team, >> >> I'm sure everyone's burned out on the OK/Cancel BUTTon discussion but >> since it was such a hot "button" topic (LOL) I thought I'd give cracking it >> a try. I'm very impressed that the window and button are as elusive to >> automation as they are, nice programming. Here's what I found: >> >> - You cannot use "Alt-O" to focus on the OK button >> - You cannot Tab through the fields to the OK button, it only sets >> focus on the cancel and then back around to the beginning field >> - Using a macro tool I could not focus the Log QSO window, it somehow >> was at the top of all windows and I couldn't "read" it using two different >> macro tools (not to be named) >> >> Things I could do: >> >> - Using a freely available macro tool I noticed I COULD query for >> open windows title bars and verify "log qso" existed >> - I could screenshot the OK button using a screenshot tool >> - Using a freely available macro toolI was able to search the screen >> for "image" of the button and specify a location to focus on, in this case >> the upper left hand where the window always pops up for me, OR if I wanted >> I probably could have moved it using the information from finding it was >> available >> - Once found the macro software focused the mouse on the coordinates >> of the "image" of the "OK button" and VOILA! I was able to "click OK" >> >> To test it I put the six line macro script loop (two of those lines were >> the loop itself) and ran it while I QSO'd with three different stations in >> the matter of a couple of minutes, each time the script was able to find >> and click the OK button wherever it landed on the LOG QSO screen. >> >> I spent about an hour fanagling with it and found two different ways to >> do it (the other way was to watch my WSJT-X computer via remote desktop or >> similar VNC and do the same "image find" dance and click remotely - this >> would probably be better because the scripting computer would have no need >> to worry or knowledge of the Z-index of the Log QSO window, it would see >> the entire screen as an image and just find the OK button regardless of >> other windows handle considerations. >> >> *So - my point is not to be a pain and hack this or explain how to do it >> but rather to postulate*, other than annoying normal users what does >> this really accomplish other than screw up the unwary button clicker when >> the OK / Cancel switch and they are too focused on the next QSO to notice >> they just nuked their first DX entry to Antarctica and missed out on >> finalizing their DXCC award? Or screwing up the visually impaired or late >> night impaired operator? >> >> If I had a vote I'd not punish the law abiding citizen and the 99% for >> the 1% abusers of automation. >> >> PS. IF you need a video of my macro I'll be glad to post it but won't to >> the group as that would make it far easier than it already is to circumvent >> this precaution. >> >> AG7GK >> >> Aaron >> >> 73 >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
