 |
Need something else than modification on .glade files! I enable Accessibility support (ATK) on my GNOME session, run Gramps with modified .glade for supporting ATK, and no change ... I suppose something must be also set on related python module? ie. call atk python module. http://www.pygtk.org/docs/pygtk/atk-class-reference.html |
|
|
I need to find good samples of pygtk applications with ATK support ... Maybe by looking at patched packages for Vinux distribution ? https://launchpad.net/~vinux/+archive/vinux-lucid Or Accessibility team ? https://launchpad.net/~accessibility https://launchpad.net/~accessibility/+related-software Related python projects: http://live.gnome.org/Accerciser https://launchpad.net/accerciser https://launchpad.net/pyspi http://git.gnome.org/browse/orca/tree/src/orca |
|
|
Some samples of use under python: # mark the root of this window with its PID so we can easily identify it # as this app root_atk = atk.get_root() root_atk.set_description(str(os.getpid())) label_acc = label_widget.get_accessible() entry_acc = entry.get_accessible() label_acc.add_relationship(atk.RelationType.LABEL_FOR, entry_acc) entry_acc.add_relationship(atk.RelationType.LABELLED_BY, label_acc) I still cannot see what this should provide as help for accessibility... No change, even by setting 'atk' into python module ! Can 'set' or 'get' description, but what should be done with this ? To make a popup ? I see no change or visual help on interface. Otherwise, under Ubuntu, we can enable some sounds on applications. Menu: Preferences -> Sound -> check "Enable sounds on windows and buttons" |
|
|
"You don't need to see anything. If you use a screenreader, or a tool for blind people, it should be able to pick it up." --Benny I need to understand what Orca (GNOME desktop) is doing with or without ATK support on a gramps session. |
|
|
Well, I tried Orca under Gnome session and this application seems very powerful for accessiblity. It works under Gramps session and make a description of (or sound for) all fields, entries, mouse action ... http://people.gnome.org/~wwalker/demos/orca-basics.html http://people.gnome.org/~wwalker/demos/orca-basics.ogv http://people.gnome.org/~wwalker/demos/test-speech.html http://people.gnome.org/~wwalker/demos/test-speech.ogv I wonder what will be more with ATK support ! Sorry, I cannot see if I am properly making the ATK support without testing it. I will make a patch against trunk for editors like said by Benny "In glade, go for the buttons of the different editors to the ATK tab (tab with icon person in wheelchair), and set a description of the Press action". |
|
|
I also try to be consistent with the privacy icon! Sometimes dialog uses "gramps-unlock" reference, sometimes it is "gtk-dialog-authentication" ! I will use "gtk-dialog-authentication" everywhere on the patch. About privacy button, there is two "press actions": lock and unlock ... I only use "Privacy" for the description. |
|
|
I get some changes done by glade editor !-<?xml version="1.0"?> +<?xml version="1.0" encoding="UTF-8"?> - <property name="has_separator">False</property> - <property name="invisible_char">●</property> + <property name="invisible_char">?</property> - <property name="orientation">vertical</property> - <!-- interface-requires grampswidgets 0.0 --> + <!-- interface-naming-policy toplevel-contextual --> + <packing> + <property name="position">0</property> + </packing> I guess it is cleanup with a more recent glade editor (3.6.7) ? |
|
|
I will also add accessible-description (a child with ability to use translations) <property name="AtkObject::accessible-description" translatable="yes" comments="Comment for translators">Description access</property> |
|
|
ATK.py (850 bytes) |
|
|
I added (atk.glade, ATK.py) a quick tool (Gramps' tool/plugin) for testing accessibility on custom widget (gramps) and button into Gramps (via menu: Tools -> Family Tree processing -> ATK...)<property name="AtkObject::accessible-name" translatable="yes">works with: ValidatableMaskedEntry, UndoableEntry, StyledTextEditor For the button, orca only reads the label! Now, I will test <property name="AtkObject::accessible-description" translatable="yes">. |
|
|
There is already some speech when we click, unclick on a button with orca. :) But how to get the label name before the clic (on mouse over) ??? What seems rather missing is the name of the image used for toggle buttons! Otherwise, to use <property name="AtkObject::accessible-name" translatable="yes"> on custom gramps widgets might help, I will add them. I need to make a new patch. Previous one will not be really useful ... I will also start a wiki page about accessibility and Gramps. |
|
|
StyledTextEditor.text (91 bytes) |
|
|
UndoableEntry.txt (6,858 bytes) |
|
|
ValidatableMaskedEntry.txt (1,017 bytes) |
|
|
I do not know if it is important, but Locality field on address, place, location editors (glade files) do not use "undoable entry" widget but the classical "GtkEntry". Others location fields use "undoable entry". |
|
|
I wonder if this accessibility pach for custom gramps widgets is useful? There is already descriptions... Missing are maybe the "accessible name" on styled text widget and some help on toggle buttons! Note, the toolbar icons on screen and edition icons on Note editor might be also improved: they use icons without label. We get the button label (OK, Cancel, Help) by using the shortcut on keyboard (ie. label on button selection versus clic on button). Strange issue is that speech on "ValidatableMaskedEntry" says "Empty field" with or without data and ignores accessibility name ... Some "undoable entries" are more accessible with accessibility names (if they do not have a related Gtk label widget) the others (with a related label widget) ignore accessibility help! |
|
|
I made a resume of investigations on a wiki section about coding and translations: Gtk label GtkLabel automaticaly generates accessibility keys on next GtkEntry and UndoableEntry fields. Remember that Gramps also uses custom widgets like StyledTextEditor and ValidatableMaskedEntry, which do not provide relation with a GtkLabel. Toggle buttons and Icons on toolbar Gramps often uses toggle buttons and alone image (no label), this excludes blind people and generates a poor interface for accessibility. Think on accessibility support when you use widgets without relation with a Gtk label or alone image on a toggle button, by adding: <property name="AtkObject::accessible-name" translatable="yes" comments="">Name access</property> Now, need to look at atk.RelationType 0005301:0021399 In python: label_acc = label_widget.get_accessible()
entry_acc = entry.get_accessible()
label_acc.add_relationship(atk.RelationType.LABEL_FOR, entry_acc)
entry_acc.add_relationship(atk.RelationType.LABELLED_BY, label_acc)I need to translate this into glade... |
|
|
Some editors are ignoring (also on 3.2.x) tooltip for Date edition: * editevent.glade * editeventref.glade see 0005312 About relationship and toggle button, I am able to link button to the related label with something like: <object class="GtkButton" id="date_stat">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="has_tooltip">True</property>
<property name="tooltip_text" translatable="yes">Invoke date editor
</property>
<property name="relief">none</property>
<accessibility>
<relation type="labelled-by" target="label209"/>
</accessibility>I wonder how we have access to the toggle button if we are blind ? see 0005308 |
|
|
TODO: look at relation between object, tooltip, focus and coding guideline: http://developer.gnome.org/accessibility-devel-guide/stable/gad-coding-guidelines.html.fr |
|
|
1. set a name for a button with image => like atk_object_set_name() 2. alternative to tooltip is the description => like atk_object_set_description() 3. for all images and icons use something => like atk_image_set_description() 4. a label for other widget should use mnemonic_widget() or a relation => like atk_relation_set_add_relation() and need to try Accerciser ... http://live.gnome.org/Accerciser |
|
|
=> need to generate a new patch according to above rules or Accerciser's output...Niveau: ERREUR Description: l'élement bouton à deux états n'a pas de nom ou d'étiquette Nom: Rôle: toggle button Hyperlien: http://live.gnome.org/Accerciser/Validate#4 Niveau: ERREUR Description: l'élément bouton à deux états n'a pas de nom ou n'a pas de description Nom: Rôle: toggle button Hyperlien: Niveau: ERREUR Description: l'élement onglet de page n'a pas de nom ou d'étiquette Nom: Rôle: page tab Hyperlien: http://live.gnome.org/Accerciser/Validate#4 Niveau: ERREUR Description: l'élement onglet de page n'a pas de nom ou d'étiquette Nom: Rôle: page tab Hyperlien: http://live.gnome.org/Accerciser/Validate#4 Niveau: ERREUR Description: l'élément actionnable boîte combinée n'est pas sélectionnable ou ne peut obtenir le focus Nom: Aperçu contient Rôle: combo box Hyperlien: http://live.gnome.org/Accerciser/Validate#1 Niveau: ERREUR Description: l'élément interactif menu n'est pas actionnable Nom: Rôle: menu Hyperlien: http://live.gnome.org/Accerciser/Validate#2 Niveau: ERREUR Description: menu n'a pas d'interface texte Nom: Rôle: menu Hyperlien: Niveau: ERREUR Description: l'élement menu n'a pas de nom ou d'étiquette Nom: Rôle: menu Hyperlien: http://live.gnome.org/Accerciser/Validate#4 Niveau: ERREUR Description: l'élement texte n'a pas de nom ou d'étiquette Nom: Rôle: text Hyperlien: http://live.gnome.org/Accerciser/Validate#4 Niveau: ERREUR Description: l'élément actionnable barre de défilement n'est pas sélectionnable ou ne peut obtenir le focus Nom: Rôle: scroll bar Hyperlien: http://live.gnome.org/Accerciser/Validate#1 |
|
|
* Above toggle button issues are related to a button with image close to 'Families Trees' string, I cannot localize it. * Above tab and combo box issues are related to Navigation bar (same into workspace with scroll bar) *Above menu issues are related to the search bar and its child "Description contains" (text and action) Move these informations into a new bug report => 0005313 |
|
|
At the end of my investigations, I will try to provide a patch against trunk for a better accessibility support. I listed the common rules on wiki: http://www.gramps-project.org/wiki/index.php?title=Accessibility#Into_Glade 1. A GtkLabel with mnemonic support will automaticaly generate accessibility keys on linked GtkEntry and UndoableEntry fields. Remember that Gramps also uses custom widgets like StyledTextEditor and ValidatableMaskedEntry, which do not always have relation with a GtkLabel. In this case, we need to set a relation. 2. Gramps often uses GtkToggleButtons and alone GtkPixmap (image without label), this excludes blind people and generates a poor interface for accessibility. Solutions could be: 1. Set mnemonic_widget() on some Gtklabel, this will generate a description for the related entry. An alternative could be to set an accessibility name on entry field. 2. Think on focus and mnemonic for buttons and description for images |
|
|
I think I get my sample/template for buttons: http://developer.gnome.org/gtk/2.24/GtkWidget.html#GtkWidget-BUILDER-UI<object class="GtkButton" id="label1"/>
<property name="label">I am a Label for a Button</property>
</object>
<object class="GtkButton" id="button1">
<accessibility>
<action action_name="click" translatable="yes">Click the button.</action>
<relation target="label1" type="labelled-by"/>
</accessibility>
<child internal-child="accessible">
<object class="AtkObject" id="a11y-button1">
<property name="AtkObject::name">Clickable Button</property>
</object>
</child>
</object>TODO: Need to re-check above patch ... |
|
|
atk.glade (14,434 bytes) |
|
|
ATK.patch (174,458 bytes) |
|
|
Added simple accelerator keys on next version (ATK.patch) <control>p : private button <control>d : date button <control>e : edition button <control>s : selector button <control>f : edition father button <control>m : edition mother button <control>a : add button where <control> is a "GDK_CONTROL_MASK". On Object Reference editors, key for the private button is only active for the reference section. Ability to make the shared record private into main object editors. TO_CHECK: does "GDK_CONTROL_MASK" works under MacOS ? 0004546 |
|
|
Patch commited against trunk (rev18380): http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=18380 |
|
|
bookreport.glade (28,665 bytes) |
|
|
Need to also look at tools (some glade files): * bookreport * ownereditor 'ownereditor' might also move to GtkBuilder for gtk+ 2.16: Pop-up menu for [copy_from_db_to_preferences] ! => 0005342 |
|
|
ownereditor.glade (19,306 bytes) |
|
|
Last 'ATK support' for 'editcitation.glade'. http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=18607 Editors should be consistent. Need to look at related/children bugs (see above links) for some specific issues. |
- Anonymous
