Re: rebuilding wx widgets with accessible addons
Nathan smith <[email protected]> Sat, 16 Nov 2024 23:49:59 +0000
| Newsgroups | gmane.comp.python.wxpython |
|---|---|
| Message-ID | <[email protected]> |
Hi Dietmar
Thanks for the information and update! :)
So, as it stands, a lot of my code runs SetName to give the widgets an=20
identifiable name, for instance:
listctrl.SetName("Files.")
for a wx.ListCtrl=C2=A0 containing a list of files.
In wx python 4.0.7, this worked to give the control an identifiable name=20
that the screen reader picked up on, but in the latest install of wx=20
python, it does not.
Same result if you pass name as an argument to the __init__
I vaguely thought I remember someone mentioning that setting the=20
accessibility flag at compile time fixed this? But maybe my memory is=20
faulty, as having spent the day looking at wx widgets, it looks like the=20
accessibility flag is set by default?
My wx version: '4.2.2 msw (phoenix) wxWidgets 3.2.6'
That's good news about the grid! I had to catch key down events and run=20
my own logic with a speech library for that.
Thanks in advance for any ideas, this is a big bummer right now as I=20
can't do anything until I figure this out, and I can't even role back to=20
python 3.8 get around things that way because another library has locked=20
itself out of 3.8.
Nathan
On 16/11/2024 20:24, Dietmar Schwertberger wrote:
> Hi Nathan,
>
> first: the wxPython-users list is almost dead.
> Most of the discussions are now on https://discuss.wxpython.org/ or on=20
> Github.
> Fortunately, Discuss has a better email option than other forum=20
> software has.
>
> I'm not sure what the modification is that you're talking about.
> Did you try the current wxPython version? In the past there were=20
> versions which had problems with the accessibility interface.
> I think that 4.0.4 to 4.0.7 had problems with Windows 32 bit builds.=20
> Others had problems related to 64 vs. 32 bit.
> I think that the latest version should behave better.
>
> In one of the next wxPython releases, you should be able to override=20
> the CreateAccessible method in Python for more customized screen=20
> reader support.
> The pull requests have been merged.
>
> There are more improvements coming once wxPython is updated to the=20
> latest wxWidgets version.
> The grid should then provide at least some basic screen reader support.
>
> In case you are wondering:
> I'm the maintainer of the wxGlade GUI builder and I have some users=20
> with screen readers. I try to support this as much as possible. The=20
> application has some options to improve accessibility, but I hope=20
> these will not be required any more with the next wxPython versions.
>
> Regards,
>
> Dietmar
>
--=20
You received this message because you are subscribed to the Google Groups "=
wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/wxpython-us=
ers/9279c686-1459-489c-9199-2e820daec1f1%40gmail.com.