I agree, but as you see, you can use that; let him tell you the status of
the flags is not all that complicated, and in the end what is functional and
accessible to the end user.
Cheers
Adriano
----- Original Message -----
From: "James Scholes" <james@xxxxxxxxxxxxx>
To: <nvda-addons@xxxxxxxxxxxxx>
Sent: Friday, March 10, 2017 5:09 PM
Subject: [nvda-addons] Re: wx, problem with list of checkboxes?
Adriano Barbieri (Redacted sender adrianobarb for DMARC) wrote:
The only thing is that I had to get him to say when a checkbox is
selected or not selected, but is perfectly accessible.
This isn't quite accurate. In your code, you explicitly tell NVDA to read the words "checked" and "unchecked" after a 100ms delay, specifically because wx.CheckListBox has accessibility problems. Don't take this the wrong way - I'm sure your solution works well enough and most users don't care how a checkbox is made accessible as long as they could use it. But it's a bit misleading to say that wx.CheckListBox is accessible without further explanation of what hacks are required to make it so.
--
James Scholes
http://twitter.com/JamesScholes
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for reporting bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe: //www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
