Difference between revisions of "Accessibility"

From Gramps
Jump to: navigation, search
m (Bugs and feature requests)
(Into Glade)
Line 24: Line 24:
  
 
===Into Glade===
 
===Into Glade===
 +
 +
In addition to accelerators, ''[http://developer.gnome.org/gtk/2.24/GtkWidget.html GtkWidget]'' also support a custom <accessible> element, which supports actions and relations. Properties on the accessible implementation of an object can be set by accessing the internal child "accessible" of a ''[http://developer.gnome.org/gtk/2.24/GtkWidget.html GtkWidget]''. See [http://developer.gnome.org/gtk/2.24/GtkWidget.html#GtkWidget-BUILDER-UI GtkBuilder UI].
  
 
* Gtk label
 
* Gtk label

Revision as of 11:24, 26 October 2011

Accessibility support

Links

  • AEGIS acronym stands for Open Accessibility Everywhere: Groundwork, Infrastructure, Standards.
  • Possibility project is a nonprofit organization dedicated to creating groundbreaking open source software for persons with disabilities.

Gramps

Gramps aims to provide the best accessibility support. Unfortunatly, all parts of the interface have not been tested for persons with disabilities. Gramps team try to do its best for a complete accessibility support.

Into Glade

In addition to accelerators, GtkWidget also support a custom <accessible> element, which supports actions and relations. Properties on the accessible implementation of an object can be set by accessing the internal child "accessible" of a GtkWidget. See GtkBuilder UI.

  • Gtk label

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.

  • Toggle buttons and Icons on toolbar

Gramps often uses GtkToggleButtons and alone GtkPixmap (image without label), this excludes blind people and generates a poor interface for accessibility.

Rules for images and buttons

  1. Set a name (eg, same as tooltip) for a button with image.
  2. Set a description for all images and icons.
<object class="GtkButton" id="date_edit">
  <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>
  <child internal-child="accessible">
    <object class="AtkObject" id="date_edit-atkobject">
      <property name="AtkObject::accessible-name" translatable="yes">Date</property>
    </object>
  </child>
  <child>
    <object class="GtkImage" id="image2264">
      <property name="visible">True</property>
      <property name="icon_name">gramps-date</property>
      <child internal-child="accessible">
        <object class="AtkObject" id="image2264-atkobject">
          <property name="AtkObject::accessible-description" translatable="yes">Date</property>
        </object>
      </child>
    </object>
  </child>
</object>

Rules for labels and buttons

  • A label for others widgets should use mnemonic_widget() or a relation.
<object class="GtkLabel" id="label2">
  <property name="visible">True</property>
  <property name="xalign">0</property>
  <property name="label" translatable="yes">La_bel:</property>
  <property name="use_underline">True</property>
  <property name="justify">center</property>
  <property name="mnemonic_widget">related_label_entry_name</property>
</object>
<object class="GtkButton" id="button1">
  <property name="visible">True</property>
  <property name="can_focus">True</property>
  <property name="receives_default">True</property>
  <accessibility>
    <relation type="labelled-by" target="label4"/>
  </accessibility>
</object>

Rules for entry

  • Set a name (eg, same as tooltip) if there is no linked mnemonic_widget() on a label.
<object class="StyledTextEditor" id="styled_text1">
  <property name="visible">True</property>
  <property name="can_focus">True</property>
  <child internal-child="accessible">
    <object class="AtkObject" id="styled_text1-atkobject">
      <property name="AtkObject::accessible-name" translatable="yes">Styled Text Editor</property>
    </object>
  </child>
</object>

Focus and tooltip

  • Think on focus for button.
<object class="GtkToggleButton" id="togglebutton1">
  <property name="visible">True</property>
  <property name="can_focus">True</property>
  <property name="has_focus">True</property>
  <property name="is_focus">True</property>
  <property name="receives_default">True</property>
  <property name="active">True</property>
  <property name="draw_indicator">True</property>
</object>
  • Think on tooltip.
<property name="has_tooltip">True</property>
<property name="tooltip_text" translatable="yes">Display a tooltip</property>

Into python

Sample

# 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)

Validate

Accerciser provides a AT-SPI Validator Plugin #5313.

Bugs and feature requests

  • #3069: GtkTreeView is very slow / crashes with Assistive Technologies / ATK / a11y enabled
  • #5301: ATK support
  • #5308: Review focus on Editors with toggle buttons
  • #5309: Review ValidatableMaskedEntry for a better Accessibility support
  • #5310: Missing Date field on MediaRef Editor
  • #5312: Make tooltip on date edition toggle button consistent
  • #5313: AT-SPI issues
  • #5314: Missing Tags environment on MediaRef Editor
  • #5320: Privacy icon/button is not consistent