Not easily. You can download CHIRP, plug in a supported radio, download its memories, then access its settings.
But what I'm asking is if these widgets should be presenting their accessible names alongside their values. If the answer is yes, then I'll capture a debug.out and go from there. If the answer is no, use this other mechanism, then I'll switch to that other mechanism. Thanks. On 03/29/2018 09:50 AM, Alex ARNAUD wrote: > Could you provide us simple steps to reproduce the issue you have? Or > a function or ui file that generate the spinbutton or combobox? > > Best regards, > Alex. > > Le 28/03/2018 à 18:49, Nolan Darilek a écrit : >> Hello, >> >> >> I'm trying to learn a bit about GTK/GNOME accessibility development. >> Recently I began dipping my toes into amateur radio, and while the Chirp >> radio programming software is highly accessible, there are some rough >> edges. The biggest of these is that programatically-created radio >> settings screens don't associate labels with their widgets. >> >> >> Chirp uses pygtk2. After it creates the widget, I use the following: >> >> >> print("Setting name", element.get_shortname(), widget) >> >> widget.get_accessible().set_name(element.get_shortname()) >> >> >> And this correctly sets the accessible name for checkboxes, text areas, >> everything but SpinBoxes and ComboBoxes. >> >> >> Am I on the right track with this? How do I associate a label with a >> Combo/Spin box such that tabbing onto it speaks the associated label? >> This works with checkboxes/text areas, so I don't know if I'm doing >> something incorrectly, or if this is an Orca issue. >> >> >> Thanks. >> >> >> _______________________________________________ >> gnome-accessibility-list mailing list >> gnome-accessibility-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list >> > _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list