GNOME Bugzilla – Bug 524541
property/signal fields not associated with labels
Last modified: 2018-03-26 15:04:41 UTC
opening up glade3 using orca with the intent to create a simple test gui as a blind developer, i sadly noticed that the properties/signals/etc frame does not have its fields associated with the respective labels. Please associate fields with labels, to enable blind/visually impaired developers to use a great tool glade et al. Other information:
Created attachment 182600 [details] This is a test source code how I need creating a dialog I confirming this issue, I am a visual impaired developer. When I want editing a vidget properties, I need examine entire screen with Orca flat review feature to hear real property labels and values, because Orca spokening only the property values, but not spokening the property labels when I jump a widget property for example with Tab key. Not possible automatical assigning property labels the real vidgets with mnemonic_widget possibility? For example, when I need creating a slider with a source code, I always creating a label vidget, and assigning the mnemonic_widget property with the slider vidget. When I jump the dialog in the slider, Orca automaticaly spokening the slider label, and the slider value, visual impaired users will be known what meaning the slider with he navigated. Now, full blind unfortunately impossible to full use Glade designer, because for example not have keystroke possibility to add vidgets with proper place in a dialog, this is another bug. Now, I need always creating GTK dialogs in source code, because this way I full "see" the dialog designing, and full possible controlling how will be looking the dialog (hopefuly). Unfortunately this way development is resulting log of redundant code, and difficulter the application maintenance. Have an another Glade related bug with related with accessibility. If you are detailed interesting, another problems and my experiences I wrote with bug 524545 bugreport. Next comment I will be attaching a wrong glade file, with demonstrating what glade file resulting if a full blind developer try designing Glade the application UI interface with only Orca usage. Because I always need reviewing entire screen, my designing need two hour this simple dialog with demonstrate the source code, and the result is wrong. Possible I doing wrong method the designing, but for example I unable to put required vidgets with proper place in the dialog with Glade designer (vbox and action area), this is described the #524545 bugreport. I very would like future developing GTK applications with visual impaired users, and future would like using Glade the designing if this two bug is fixed. Attila
Created attachment 182601 [details] This is a wrong glade file
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glade/issues/25.