[chirp_users] chirp and screen reader accessibility
Just a thought here but I wonder if the developers have given consideration to building screen reader accessibility in to the program? Presently, Chirp does not work well if at all with any of the commonly and widely used text to speech screen reading programs such as JAWS and NVDA. The NVDA screen reader is an open source program so its developers may be more receptive to working to build accessibility into Chirp. This question may have come up before and if it has, I apologize in advance. http://www.nvda-project.org
Ray T. Mahorney WA4WGA
It does work well in Linux with the screenreader Orca. It is not hard to learn what you need to use to operate Chirp. In fact, you can download a distro and boot it up with Orca and Chirp ready to go. Maybe you know this, but I thought I'd mention it just in case. Glenn
----- Original Message ----- From: Ray T. Mahorney via chirp_users To: chirp_users@intrepid.danplanet.com Sent: Friday, January 26, 2018 6:59 PM Subject: [chirp_users] chirp and screen reader accessibility
Just a thought here but I wonder if the developers have given consideration to building screen reader accessibility in to the program? Presently, Chirp does not work well if at all with any of the commonly and widely used text to speech screen reading programs such as JAWS and NVDA. The NVDA screen reader is an open source program so its developers may be more receptive to working to build accessibility into Chirp. This question may have come up before and if it has, I apologize in advance. http://www.nvda-project.org
Ray T. Mahorney WA4WGA
--------------------------------------------------------------------------------
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
edited to make a bit more accurate.
Ray, I have brought this to the attention of this group several times over the last several years. My impression is that they are not interested. I also get referred to the Linux OS version, which is "mostly" accessible. I say mostly as there are some controls in the save file dialog that aren't clearly explained.
As a reference to my first sentence. It's not really that they are not interested. It is (given the nature of python) a little more difficult to make it accessible in any version of windows. However, it's not impossible. there are some accessibility routines and libraries built into python )those modules only need to be added) that make python compiled programs fully accessible (look at what bittorrent.com did with their client. It's fully accessible on OS X and Linux and could be made that way in windows with a few small tweaks). Now, admitted, the larger share of the problem is the windows interface and their MSAA).
anyway, I hope this clears up things.
DE n7zzt Eric
On Jan 26, 2018, at 5:59 PM, Ray T. Mahorney via chirp_users wrote:
Just a thought here but I wonder if the developers have given consideration to building screen reader accessibility in to the program? Presently, Chirp does not work well if at all with any of the commonly and widely used text to speech screen reading programs such as JAWS and NVDA. The NVDA screen reader is an open source program so its developers may be more receptive to working to build accessibility into Chirp. This question may have come up before and if it has, I apologize in advance. http://www.nvda-project.org
Ray T. Mahorney WA4WGA _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eric Oyen at eric.oyen@icloud.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Rather than "brought this to the attention of this group several times over the last several years"
why not offer to assist with the software development?
It is likely that nobody on the team has ever used a screen reader or knows what is required both of the reader and how to make it work.
On 27 January 2018 at 15:29 Eric Oyen eric.oyen@icloud.com wrote:
edited to make a bit more accurate. Ray, I have brought this to the attention of this group several times over the last several years. My impression is that they are not interested. I also get referred to the Linux OS version, which is "mostly" accessible. I say mostly as there are some controls in the save file dialog that aren't clearly explained. As a reference to my first sentence. It's not really that they are not interested. It is (given the nature of python) a little more difficult to make it accessible in any version of windows. However, it's not impossible. there are some accessibility routines and libraries built into python )those modules only need to be added) that make python compiled programs fully accessible (look at whathttp://bittorrent.com did with their client. It's fully accessible on OS X and Linux and could be made that way in windows with a few small tweaks). Now, admitted, the larger share of the problem is the windows interface and their MSAA). anyway, I hope this clears up things. DE n7zzt Eric On Jan 26, 2018, at 5:59 PM, Ray T. Mahorney via chirp_users wrote: > > Just a thought here but I wonder if the developers have given consideration to building screen reader accessibility in to the program? Presently, Chirp does not work well if at all with any of the commonly and widely used text to speech screen reading programs such as JAWS and NVDA. The NVDA screen reader is an open source program so its developers may be more receptive to working to build accessibility into Chirp. This question may have come up before and if it has, I apologize in advance.http://www.nvda-project.org/Ray T. Mahorney WA4WGA _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eric Oyen at eric.oyen@icloud.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com >
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032 Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel@ngunn.net www http://www.ngunn.net Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club International #385, Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382.
participants (4)
-
Eric Oyen -
Glenn At Home -
Nigel A. Gunn G8IFF/W8IFF -
Ray T. Mahorney