gmane.comp.gnome.accessibility.devel

ANNOUNCE: AT-SPI 2.5.1 released

Mike Gorse — 2012-04-30T21:39:43

AT-SPI 2.5.1 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.5/
http://download.gnome.org/sources/at-spi2-atk/2.5/
http://download.gnome.org/sources/pyatspi/2.5/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.5.1

* [core/pyatspi] Add atspi_set_timeout.

* [core] By default, disable method call timeouts until an application has
been on the bus for 15 seconds (work-around for applications with potentially
long start-up times). This behavior can be changed with a call to
atspi_set_timeout.

* [core] Fix GError sent when receiving a reply of the wrong type

* [core] Fix typo in atspi_document_get_attribute_value

* [core] Fix for bug 675004 - object:state-changed:defunct events are emitted
as object:state-change:defunct

* [atk] Updated Norwegian Nynorsk translation

* [pyatspi] Some clean-ups for Python 3.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

About proposing "accessibility on by default" as feature

Piñeiro — 2012-04-20T16:15:13

Hi,

some context: on last ATK/AT-SPI2 accessibility hackfest [1] one of the
ideas that came again to the table was proposing to set accessibility
support on by default. That work would include having the accessibility
nits running all the time, without a accessibility-toolkit setting
switch, and also stop to having the accessibility code loaded as
plugins. At this moment the only remaining plugin is the atk-bridge, so
the idea is having the same functionality as a library call. Something
like a atk_bridge_init (..) call (equivalent to gtk_init).

On our last accessibility meeting we were talking about proposing this
as a new 3.6 feature, as seems a good way to start the discussion with
the community. From that meeting:
Apr 19 16:10:13 <API>    #action Piñeiro after some researching, will
bring the having accessibility by default 3.6 to the accessibility list
Apr 19 16:10:32 <API>    #action Piñeiro after some debate we could
propose it as feature

So after that research I'm here to talk about this (output of that
research at the appendix of this mail).

So lets see the current situation:
 * Accessibility performance and stability has been improving during the
last two releases.
 * GNOME-Shell (for user POV, GNOME) accessibility has improved with the
last release.
 * But there are still several core applications (ie: evolution) without
a proper accessibility support (also crash-prone)
 * Now it is possible to enable accessibility on runtime, without
requiring the uncomfortable logout
 * Most of the bus traffic is not sent unless one AT is listening

As we mentioned on the meeting, having the accessibility running would
provide more testing on the accessibility framework, both on runtime and
on compiling time (as at-spi2-[core/atk] will became a compiling
dependency).

The problems I see are:
  a) About having accessibility enabled all the time: right now
activating the accessibility on runtime works, so some people would be
against adding an inherent risk
  b) About stop to using plugins: some people will not like adding a new
dependency to their projects (this could be irrelevant if the final
solution is add that call on ATK, as randomly suggested on the hackfest)
  c) Although we agree that we want to stop to load the bridge as a
plugin, we are still not sure about how and where implement it.
  d) We didn't debated how all this changes would affect GTK2 apps.
Because the fact is that there are apps still not ported.
  e) My inner pessimist thinks that getting to a conclusion, implement
it, integrate it and test it are too much, and it would be difficult to
have all ready for 3.6

Finally, comment that probably there is a compromise option, that is:
 * Keep working on c), as seems the way to go. Probably with unstable
branches of atk, at-spi, gtk and clutter
 * For this cycle just propose to change the default value of
accessibility-toolkit. In that case we would still have more runtime
testing, and it would be easy to go back if things are failing. If
things are not failing, it would be a good way to minimize a) if we
propose to remove the gsetting switch.

With that compromised option, for this cycle we would just propose to
change the default value of accessibility-toolkit, while working on the
other stuff.

So, ideas, thoughts?

***

Appendix (somewhat offtopic or this mail main topic)
That research that I wanted to do was check why the following was working:
 1. accessibility-toolkit is disabled
 2. gnome-shell is running
 3. Via Universal-Settings you activate "Screen reader", this sets
accessibility-toolkit as enabled
 4. Orca interacts properly with gnome-shell

The "classical GNOME accessibility" wisdom tell us that 4 is not
possible, and you need a logout. Also take into account that gnome-shell
has a custom code that loads that module if that gsetting is enabled.
With GTK3 this was not required anymore thanks to the gsettings-daemon
magic, and the at-spi2-atk.desktop file, that informs that when
accessibility-toolkit became enabled, it should load the bridge.

So, how gnome-shell does that? Well ... thanks to gsettings-daemon, as
gnome-shell also calls gtk_init, so it is also a GTK app. In fact, if
you remove that custom loading-code, in some situations it is still
working (note "some situations", so we can't remove that code yet). As
you can guess, those "some situations" are exactly the situations we
were expecting this all to be failing. In the same way, that
"NO-AT-BRIDGE" "NO-GAIL" code is still required to ensure that AtkUtil
implementation of GTK is not loaded. Yes, all this seems tricky and
fragile, and for sure requires some cleaning, but for now it is working.

BR

[1]
http://blogs.igalia.com/apinheiro/2012/01/24/atkat-spi2-hackfest-2012-days-2345/

ANNOUNCE: at-spi2-core 2.4.1 released

Mike Gorse — 2012-04-16T19:37:44

At-spi2-core 2.4.1 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.4/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.4.0

* Fix a GError set when a method call returns a reply of the wrong type.

* Do not time out method calls for the first 15 seconds that an
   application is on the bus (work-around for Orca setting an application's
   script as "default" after a timeout on a slow-starting application).


Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

at-spi2 and a11ytesting core dump

Patrick Welche — 2012-04-05T11:17:04

I am getting a repeatable core dump from ldtp when running the gcalctool.xml
test from a11ytesting (bin/mago --log-level=debug -a a11y -f gcalctool.xml):

Core was generated by `python2.6'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f7ff77d66c0 in ?? ()
(gdb) bt
#0  0x00007f7ff77d66c0 in ?? ()
#1  0x00007f7fe0e12e05 in _atspi_send_event (e=0x7f7fffffa430)
    at atspi-event-listener.c:817
#2  0x00007f7fe0e13390 in _atspi_dbus_handle_event (bus=0x7f7ff6788400, 
    message=0x7f7ff77069e0, data=0x0) at atspi-event-listener.c:944
#3  0x00007f7fe0e15c18 in process_deferred_message (closure=0x7f7ff2319320)
    at atspi-misc.c:673
#4  0x00007f7fe0e15d2d in _atspi_process_deferred_messages (data=0x0)
    at atspi-misc.c:703
#5  0x00007f7ff0c3ffd2 in g_main_context_dispatch ()
   from /usr/pkg/lib/libglib-2.0.so.0

(gdb) frame 1
#1  0x00007f7fe0e12e05 in _atspi_send_event (e=0x7f7fffffa430)
    at atspi-event-listener.c:817
817             entry->callback (atspi_event_copy (e), entry->user_data);
(gdb) print e
$1 = (AtspiEvent *) 0x7f7fffffa430
(gdb) print *e
$2 = {type = 0x7f7ff23197c0 "object:children-changed:add", 
  source = 0x7f7ff2ff2810, detail1 = 0, detail2 = 0, any_data = {
    g_type = 140187568332640, data = {{v_int = -218158304, 
        v_uint = 4076808992, v_long = 140187514383136, 
        v_ulong = 140187514383136, v_int64 = 140187514383136, 
        v_uint64 = 140187514383136, v_float = -1.0108264e+31, 
        v_double = 6.9261834832583127e-310, v_pointer = 0x7f7ff2ff2b20}, {
        v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, 
        v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}}
(gdb) print *entry
$3 = {callback = 0x7f7ff77d66c0, user_data = 0x7f7ff2ff8c50, 
  callback_destroyed = 0x7f7ff77d65c0, category = 0x7f7ff7703c50 "Object", 
  name = 0x7f7ff77d3a20 "ChildrenChanged", detail = 0x0}


The test box is using (at-spi2-core, at-spi2-atk, pyatspi) all version 2.4,
ldtp 2.3.0, accerciser 3.4.0. (i.e., latest tar balls)

One oddity is that the terminal in which ldtp -v is running generates:
(LDTB_DEBG 2 is set)

ldtp -v
sem_wait: Invalid argument
sem_post: Invalid argument
sem_wait: Invalid argument
sem_post: Invalid argument
sem_wait: Invalid argument
Segmentation fault (core dumped)

Who is using semaphores? (A quick look doesn't find any in at-spi2-core,
accerciser nor ldtp - have I missed some?)


The only trivial change I made to a11ytesting was:

--- mago/cmd/result.py  2011-10-09 16:01:33 +0000
+++ mago/cmd/result.py  2012-04-05 11:10:55 +0000
< at > -45,4 +45,4 < at >< at >
           self.append('screenshot', _logFile)
         except:
           # Screenshots fail to connect to xmlrpc socket in GNOME 3.0
-          self.append('screenshot failed',_logFile)
+          self.append('screenshot_failed',_logFile)

so I basically have no local modifications in the long string of
dependencies...


Any thoughts on where to look?

Cheers,

Patrick

ANNOUNCE: AT-SPI 2.4.0 released

Mike Gorse — 2012-03-26T21:05:20

AT-SPI 2.4.0 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.4/
http://download.gnome.org/sources/at-spi2-atk/2.4/
http://download.gnome.org/sources/pyatspi/2.4/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.4.0

* [core] Fix typo in at-spi-dbus-bus.desktop.in (BGO#605662).

* [core/atk] Updated Hindi translation.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

ATK 2.4.0 released

Piñeiro — 2012-03-26T18:59:31

About ATK
=========

GNOME provides support for accessibility devices using the ATK
framework. This framework defines a set of interfaces to which
graphical interface components adhere. This allows, for instance,
screen readers to read the text of an interface and interact with its
controls. ATK support is built into GTK+ and the rest of the GNOME
platform, so any application using GTK+ will have reasonable
accessibility support for free.

Nonetheless, you should be aware of accessibility issues when when
developing your applications. Although GTK+ interfaces provide
reasonable accessibility by default, you can often improve how well
your program behaves with accessibility tools by providing additional
information to ATK. If you develop custom widgets, you should ensure
that they expose their properties to ATK. You should also avoid using
sound, graphics, or color as the sole means of conveying information
to the user.

The GNOME desktop ships with a number of accessibility tools which
enable users with disabilities to take full advantage of their desktop
and applications. Applications that fully implement ATK will be able
to work with the accessibility tools. GNOME's accessibility tools
include a screen reader, a screen magnifier, an on-screen keyboard,
and Dasher, an predictive text entry tool.

News
====

* Bug 593220: Some typos in atktable signals (docs)
* Updated Hindi and Simplified Chinese translation


Contributors
============

Daniel Mustieles, Alejandro Piñeiro Iglesias,

Translations
============

* Automatic Mirroring (zh_CN)
* Rajesh Ranjan (hi)


Download
========

http://download.gnome.org/sources/atk/2.4/atk-2.4.0.tar.xz (593K)
  sha256sum:
091e9ce975a9fbbc7cd8fa64c9c389ffb7fa6cdde58b6d5c01b2c267093d888d

ANNOUNCE: AT-SPI 2.3.92 released

Mike Gorse — 2012-03-20T21:00:37

AT-SPI 2.3.92 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.3/
http://download.gnome.org/sources/at-spi2-atk/2.3/
http://download.gnome.org/sources/pyatspi/2.3/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.3.91

* [core] Some changes to try to prevent at-spi2-registryd from incorrectly
   thinking that an AT is hung and passing keys meant for it to the application.

* [core] Fix crash fetching an error from a reply when retrieving a property.

* [atk] Add Khmer and Malayalam translations.

* [pyatspi] Another fix for --enable-tests.


Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

ATK 2.3.95 released

Piñeiro — 2012-03-19T23:36:49

About ATK
=========

GNOME provides support for accessibility devices using the ATK
framework. This framework defines a set of interfaces to which
graphical interface components adhere. This allows, for instance,
screen readers to read the text of an interface and interact with its
controls. ATK support is built into GTK+ and the rest of the GNOME
platform, so any application using GTK+ will have reasonable
accessibility support for free.

Nonetheless, you should be aware of accessibility issues when when
developing your applications. Although GTK+ interfaces provide
reasonable accessibility by default, you can often improve how well
your program behaves with accessibility tools by providing additional
information to ATK. If you develop custom widgets, you should ensure
that they expose their properties to ATK. You should also avoid using
sound, graphics, or color as the sole means of conveying information
to the user.

The GNOME desktop ships with a number of accessibility tools which
enable users with disabilities to take full advantage of their desktop
and applications. Applications that fully implement ATK will be able
to work with the accessibility tools. GNOME's accessibility tools
include a screen reader, a screen magnifier, an on-screen keyboard,
and Dasher, an predictive text entry tool.


News
====

* Bug 671857: Add deprecation attributes to deprecated functions
* Updated Visual Studio configuration files


Contributors
============

Chun-wei Fan, Javier Jardón, Alejandro Piñeiro Iglesias,

Translations
============

* bn_IN, courtesy of Runa Bhattacharjee
* km, courtesy of Morn Met
* ml, courtesy of Anish A


Download
========

http://download.gnome.org/sources/atk/2.3/atk-2.3.93.tar.xz (589K)
  sha256sum:
b551078c69132202d310afd180cac87c6f67e14f842a5fadde251479884db2f9

ATK 2.3.93 released

Piñeiro — 2012-03-07T12:40:30

About ATK
=========

GNOME provides support for accessibility devices using the ATK
framework. This framework defines a set of interfaces to which
graphical interface components adhere. This allows, for instance,
screen readers to read the text of an interface and interact with its
controls. ATK support is built into GTK+ and the rest of the GNOME
platform, so any application using GTK+ will have reasonable
accessibility support for free.

Nonetheless, you should be aware of accessibility issues when when
developing your applications. Although GTK+ interfaces provide
reasonable accessibility by default, you can often improve how well
your program behaves with accessibility tools by providing additional
information to ATK. If you develop custom widgets, you should ensure
that they expose their properties to ATK. You should also avoid using
sound, graphics, or color as the sole means of conveying information
to the user.

The GNOME desktop ships with a number of accessibility tools which
enable users with disabilities to take full advantage of their desktop
and applications. Applications that fully implement ATK will be able
to work with the accessibility tools. GNOME's accessibility tools
include a screen reader, a screen magnifier, an on-screen keyboard,
and Dasher, an predictive text entry tool.


News
====

* Revert "Using abstract atk_object_get_name to check accessible-name
*  notification" change made on 2.3.93
*  Related to mozilla bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=733712


Download
========

http://download.gnome.org/sources/atk/2.3/atk-2.3.93.tar.xz (589K)
  sha256sum:
b551078c69132202d310afd180cac87c6f67e14f842a5fadde251479884db2f9

ATK STATE_EDITABLE

Alexander Surkov — 2012-03-07T06:45:52

Hi. There's interesting discussion about editable vs unavailable state
happening at Mozilla bug -
https://bugzilla.mozilla.org/show_bug.cgi?id=733382. I put here some
summary of it.

The ATK spec says: "Indicates the user can change the contents of this
object" - http://www.pygtk.org/docs/pygtk/atk-constants.html#atk-state-type-constants.
That means readonly and disabled text controls shouldn't be exposed as
editable. ATs might be interested to know whether the object is
potentially editable to put it into navigation order. Also that makes
it similar to other 'able' states like expandable or multiselectable
except focusable state which is sort of opposite to absent enabled
state. So let's consider an exampe:

<p contentEditable="true" aria-disabled="true">

Currently: no enabled state, no editable state. This paragraph exposed
absolutely identically to plain <p>.
Proposed: no enabled state, editable state is presented. AT understand
this paragraph is sort of control and can be used for typing when
enabled.

Please let me know what you think.

Thank you.
Alex

ANNOUNCE: AT-SPI 2.3.91 released

Mike Gorse — 2012-03-06T00:44:02

AT-SPI 2.3.91 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.3/
http://download.gnome.org/sources/at-spi2-atk/2.3/
http://download.gnome.org/sources/pyatspi/2.3/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.3.91

* [core] Fix for BGO#668334: Set correct end offset in
   atspi_text_get_attributes.

* [core] Add some type checking on method replies; this should prevent crashes
   if an application-side AT-SPI implementor returns something unexpected.

* [core] Call g_settings_sync after updating toolkit-accessibility.

* [core] Add ScreenReaderEnabled D-Bus property as a proxy for the GSettings
   key.

* [core] Fix for BGO#669344: Don't use "restrict" as a variable name, since it
   can be a keyword.

* [atk] Remove the ability to set an accessible's name and description via
   AT-SPI (it seems wrong to have been exposing this in the first place).

* [atk] Fix for BGO#659967: some list API usage fixes.

* [atk] Fix for BGO#663967: Don't use /a11y/ as a dconf path.

* [atk] Fix for BGO#666371: possible crash when accessibles are created and
   deleted in rapid succession; eg, in gnome-shell)

* [atk] Avoid triggering GLib criticals in a few places.

* [pyatspi] Fix for BGO#660826: Drop unneeded pygtk check.

* [pyatspi] Remove exception wrapping - pyatspi will now return the real
   exception as translated by pygi, rather than LookupError. This means that it
   is now necessary to catch, eg, RuntimeError rather than LookupError if one
   wishes to catch exceptions, but it is now possible to see the original error.

* [core] Invalidate states when receiving a focus event (BGO#663992).

* [core] Fix atspi_table_get_row_column_extents_at_index.

* [core/atk] Use a signed intt for GetIndexInParent, per the spec.

* [core] Send key events to listeners assumed to be hung, but don't block.

* [core] Reduce the method call timeout slightly, so that it will be lower than
   the keystroke listener timeout.

* [core] Don't cache data for transient objects.

* [core] Enable caching on a call to atspi_accessible_set_cache_mask, even if
   atspi-event_main() hasn't been called.

* [atk] Send a DoAction reply message before invoking atk (works around
   atk_action_do_action potentially not returning right away for gtk).

* [pyatspi] Fix an issue with --enable-tests.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

ATK 2.3.91 released

Piñeiro — 2012-03-06T00:32:22

About ATK
=========

GNOME provides support for accessibility devices using the ATK
framework. This framework defines a set of interfaces to which
graphical interface components adhere. This allows, for instance,
screen readers to read the text of an interface and interact with its
controls. ATK support is built into GTK+ and the rest of the GNOME
platform, so any application using GTK+ will have reasonable
accessibility support for free.

Nonetheless, you should be aware of accessibility issues when when
developing your applications. Although GTK+ interfaces provide
reasonable accessibility by default, you can often improve how well
your program behaves with accessibility tools by providing additional
information to ATK. If you develop custom widgets, you should ensure
that they expose their properties to ATK. You should also avoid using
sound, graphics, or color as the sole means of conveying information
to the user.

The GNOME desktop ships with a number of accessibility tools which
enable users with disabilities to take full advantage of their desktop
and applications. Applications that fully implement ATK will be able
to work with the accessibility tools. GNOME's accessibility tools
include a screen reader, a screen magnifier, an on-screen keyboard,
and Dasher, an predictive text entry tool.


News
====

* Bug 665549: add sanity-check of atk_text_get_text
* Bug 668441: atk_action_get_keybinding docs are confusing and need
*  updating
* Using abstract atk_object_get_name to check accessible-name
*  notification


Translations
============

* be, courtesy of Kasia Bondarava
* et, courtesy of Mattias Põldaru
* hu, courtesy of Attila Hammer
* nb, courtesy of Kjartan Maraas
* tr, courtesy of Muhammet Kara
* ug, courtesy of Sahran
* uk, courtesy of Korostil Daniel

Download
========

Tarball is available in the following location on ftp.gnome.org:

  http://download.gnome.org/sources/atk/2.3/

5531d23434bc458145651bea57d6f22e6a5ac264f6d60794102173454e1cb75a
atk-2.3.91.news

7faaddda8c2fb537ef90c4816d747ca4ec1085350ad3713c3cb904e93cfec463
atk-2.3.91.tar.xz

Health & Accessibility topic of LSM 2012

Samuel Thibault — 2012-03-01T01:27:58

LSM/RMLL 2012
                 13th Libre Software Meeting
                      July 7-12, 2012
                     Geneva, SWITZERLAND
                   http://2012.rmll.info/
              Call For Papers and Participation
           limited on health & accessibility topic
     [we apologize for duplicate receipt of this message]
         Last call before deadline : march *31* 2012


Dear Colleague,

The 13th Libre Software Meeting (LSM) takes place in Geneva,
Switzerland, July 7-12 2012 (http://2012.rmll.info/).

LSM is an annual non-commercial conference on Libre Softwares that
includes round tables and practical workshops. The objective is
to provide a place where users, developers and promoters of Libre
Software can exchange ideas and information. Attendance is free and
open to everyone. 

Each year the health & accessibility workshop is held as part of
this broader meeting.  This year, it will be organized around 3
major fields:

- Accessibility, autonomy and dependency management (mobile/web
accessibility, accessible desktop applications, usability, ...)

- Hospital information system & Tele-health (EHR, telemedicine systems,
workflow solutions, PACS, HL7, ...)

- Imaging & visualization of medical data (CAS, CAD, bio-imaging,
image acquisition/processing/segmentation/registration, simulation,
organ tracking ...)
We invite presentations that address these major fields.

The LSM committee aims to disseminate and improve Libre projects
in the health and accessibility domains through this workshop. To
better target the various exchanges that will be taking place, the
programme committee of the health & accessibility workshop proposes
several kinds of meetings:

- "Solution" meetings, with conferences  and round tables to present
solutions dedicated to previous areas.

- "State of the art" conferences between practitioners, developers,
scientists and users to discuss about what exists according to the
specific needs of users, what works well or a little less well,
to talk about approaches...

- "Technical" presentations between developers and scientists. This
will allow initiation of exchanges between communities that do not
necessarily have the opportunity to meet and will maybe lead to new
collaborations or projects.

Finally, a workshop area will be available to try out and exchange
tools presented by their authors or by seasoned users of those
solutions.


Last year the health & accessibility workshop received (for example)
the following projects: Chewing Word, drupal, FreeMedForms, GDCM,
ITK, joomla kaekus, odt2braille, OpenStreetMap, OsiriX, typo3, ubuntu,
VTK, WEASIS, wordpress, ...

... Information on health workshops from previous annual meetings
are available on :
- http://2011.rmll.info/-Sante-accessibilite-et-handicap-?lang=en
You will be able to attend conferences  on other related issues
such as "System Administration" (like Nagios, GLPI, Cfengine,
...), "Development" (like NoSQL, Lucene, GCC, ...), "Law" (like
Licenses,OpenData, FSF, ...), "Internet" (WebGL, Jabber, Typo3, ...),
... All previous conferences are available on :
- http://2011.rmll.info/-Programme-?lang=en

This year, LSM will have also 3 transversal topics (thread) :

  • Cloud

  • Common goods

  • "Libre" economy


If you are interested to participate, please submit your presentation
at:
http://call.rmll.info/talk/new

Please feel free to share this information with others people who
may be interested. We welcome your participation and input and look
forward for a valuable meeting. 

*IMPORTANT* *DATES*:
- The deadline for submission is 31 March 2012. 
- The list of accepted presentations will be announced 15 April, 2012.
- Meeting: July 7-12, 2012.

*ABSTRACT* *SUBMISSION*:
- The call for papers is available here:
 EN : http://2012.rmll.info/participer/call-for-papers
 DE : http://2012.rmll.info/participer/call-for-papers-deutsch
 FR : http://2012.rmll.info/participer/appel-a-conferences

- And you can answer on :
 http://call.rmll.info/
 (Note, you can submit in *english* or *french*)

Best regards,
Programme Commitee of the LSM 2012 health/accessibility topic
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel< at >gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

at-spi2 testing

Patrick Welche — 2012-02-23T18:56:26

Before I dig further, this may be obvious to one of you...

dbus-launch, at-spi-bus-launcher and at-spi2-registryd are running.

at-spi-bus-launcher provides org.a11y.Bus

org.a11y.Bus.service (and org.a1y.atspi.Registry.service) are in
share/dbus-1/services

orca 3.3.90 however is dying at line 44 of settings_manager.py:

  _proxy = _bus.get_object("org.a11y.Bus", "/org/a11y/bus")

Trying this from within a python prompt gets me:

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited:
  Launch helper exited with unknown return code 0

Does this ring a bell with anyone?

Cheers,

Patrick

(BTW I got to the bottom of that "orca configure finds python modules which
aren't installed" problem, and wrote up the explanation for a 1 word fix in
Bug 670685)

ANNOUNCE: AT-SPI 2.3.90 released

Mike Gorse — 2012-02-20T23:45:51

AT-SPI 2.3.90 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.3/
http://download.gnome.org/sources/at-spi2-atk/2.3/
http://download.gnome.org/sources/pyatspi/2.3/ [latest is pyatspi 2.3.5]

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.3.90

* [core] At-spi-bus-launcher now emits PropertiesChanged signals from the
   correct interface.

* [cire] If a keystroke listener does not respond, disable it until it
   responds.  This prevents the desktop from locking up if an AT hangs or is
   suspended and has a keyboard listener registered.

* [core] Fix a warning when a NULL object is returned as the detail of an
   event.

* [atk] Have GrabFocus return a bool, per the spec, rather than a uint32.

* [atk] Fix a potential crash when emitting a signal if the ATK implementor
   misbehaves.


Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

ANNOUNCE: AT-SPI 2.3.5 released

Mike Gorse — 2012-02-07T04:57:29

AT-SPI 2.3.5 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.3/
http://download.gnome.org/sources/at-spi2-atk/2.3/
http://download.gnome.org/sources/pyatspi/2.3/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.2.3

* [core] Fix for BGO#668334: Set correct end offset in
   atspi_text_get_attributes.

* [core] Add some type checking on method replies; this should prevent crashes
   if an application-side AT-SPI implementor returns something unexpected.

* [core] Call g_settings_sync after updating toolkit-accessibility.

* [core] Add ScreenReaderEnabled D-Bus property as a proxy for the GSettings
   key.

* [core] Fix for BGO#669344: Don't use "restrict" as a variable name, since it
   can be a keyword.

* [atk] Remove the ability to set an accessible's name and description via
   AT-SPI (it seems wrong to have been exposing this in the first place).

* [atk] Fix for BGO#659967: some list API usage fixes.

* [atk] Fix for BGO#663967: Don't use /a11y/ as a dconf path.

* [atk] Fix for BGO#666371: possible crash when accessibles are created and
   deleted in rapid succession; eg, in gnome-shell)

* [atk] Avoid triggering GLib criticals in a few places.

* [pyatspi] Fix for BGO#660826: Drop unneeded pygtk check.

* [pyatspi] Remove exception wrapping - pyatspi will now return the real
   exception as translated by pygi, rather than LookupError. This means that it
   is now necessary to catch, eg, RuntimeError rather than LookupError if one
   wishes to catch exceptions, but it is now possible to see the original error.


Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus



How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

ANNOUNCE: AT-SPI 2.3.4 released

Mike Gorse — 2012-01-16T03:57:01

AT-SPI 2.3.4 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.3/
http://download.gnome.org/sources/at-spi2-atk/2.3/
http://download.gnome.org/sources/pyatspi/2.3/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.


What's changed in AT-SPI 2.2.3

* [core] Add some dbus message signature checks.

* [core] Fix a crash if a device listener incorrectly returns a non-bool.

* [core/atk] Fix for BGO#666870: Keystroke listeners do not work unless an
   event listener is also registered [both modules need to be updated]

* [core] Fix for BGO#667254: Some atspi-selection_* functions were broken.

* [core] When a call times out, ping the connection and avoid making subsequent
   calls until the ping is answered.

* Fix for BGO#666871: deregisterKeystrokeListener was broken.


How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi< at >lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

GNOME3

Smitten — 2012-01-13T20:30:53

Needing to vent, and possible open some minds to the problems suffered by
some.

I am disabled. I have days when I cannot control my body. Still, I'm very
fortunate. I do have good days. When I am able I build, from donated
computers, boxes which I donate to local nursing homes. I also maintain
those boxes and teach residents how to use them.

One such resident had an accident in her teens. She's now in her late 30's
early 40's. She has almost no control over her body. She does have limited
control over two fingers. She controls her wheelchair this way. She cannot
speak clearly or write. For most of her life she has been unable to
communicate well. She had a cardboard keyboard with letters, numbers and
symbols which she carries with her to "talk" to people. It gave me the idea
of downloading and installing a keyboard for the screen. Someone donated a
rollerball mouse. The staff mounted it to the desk and also mounted a strap
to keep her hand on the mouse.

For the first time since her accident, she can talk freely with her sister.
It may take an hour for a simple eMail, but it has revitalized her world.
The staff are wonderful. They take the time to wait with her and help her
over some of the rough spots.

The old way was a simple panel icon she could click on to bring up GMail,
and another to bring up the keyboard. I just upgraded my system to Fedora
15. I know that puts me behind, but as I always encounter problems with
each new version, I tend to procrastinate. As I said, I am disabled as well.

Setting up GNOME3 to allow me to use desktop icons was a difficult process.
I  have learned many new things, which I admit I enjoy, but it has
instilled a fear in me that GNOME will disable the tools I used and lock
out changes to what they consider "pretty."  I have learned about
dconf-editor and used it to bring back the desktop and icons. I tried the
Tweak tool, but it was very limited. I think she can use the system, so I'm
going to upgrade the computer at the nursing home to 15.

Despite the fixes I made, there are still problems. GNOME3 forces her to
click on "Activities" to bring up a menu, to which she has to navigate,
only to click on another menu, to which, after positioning her mouse to
click again, she has to navigate through a bunch of icons, to click on the
program she wishes to access.  Gods. That's just bordering on cruelty.
She's limited to the icons I can save to the desktop.

I am not nearly as disabled as she, but I still have my problems. I often
position my mouse, only to have my hand twitch as I try to click and end up
opening an entirely unintended program. It's frustrating. I liked the old
way better where everything was grouped together. I would still make
mistakes, but it didn't take so long to go through the process again.

Thanks for listening.
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel< at >gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

The proper GTK+ accessibility modules loading

Michael Pozhidaev — 2012-01-08T01:01:53

Hi!

I have the question about the proper gail and atk-bridge modules loading
for GTK+ application to enable their accessibility. At first orca
startup it asks usual questions and make some changes to enable GNOME
accessibility. On next GNOME launch at-spi2-registryd is present in
processes list but orca speaks only its greeting. The command "export
GTK_MODULES=gail:atk-bridge" before GTK-based application startup
(including orca itself) lets me enable proper accessibility  navigation
inside of this application but I don't know how these modules must be
loaded automatically for every application inside of GNOME
environment. Please, give me any  recommendation how I can debug this
problem!

Currently I have on my system libgtk+-3.2.3, at-spi2-core-2.2.3 and
orca-3.2.2. I am using ALT Linux distribution. It is not based on Debian
or Ubuntu packages so the problem can be caused by incorrect GNOME
components packaging.

Thanks!

Text alternatives and GtkPixbuf [Was: GNOME LaunchesCampaign for Accessibility]

Benjamin Hawkes-Lewis — 2012-01-07T18:09:30

The maintainer on the bugs for which you provided patches agreed that
GTK should provide that opportunity.

But they argued that text alternatives should be stored in the data
structures containing GtkPixBuf, not in the GtkPixBuf data structure
itself.

The equivalent structure in QT appears to be QPixmap, and as far as I
can tell this does not contain text alternatives either:

   https://developer.qt.nokia.com/doc/qt-4.8/qpixmap.html

So I'm sceptical of your analysis of why the Qt icons talk, but maybe
you can elaborate on how this works in terms of the QT data structure
hierarchy?

What would be the problem with adding text alternatives higher in the
GTK object hierarchy, for example at the GtkCellRendererPixBuf level?

   http://developer.gnome.org/gtk/2.24/GtkCellRendererPixbuf.html

--
Benjamin Hawkes-Lewis
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel< at >gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

The proper GTK+ accessibility modules loading

Michael Pozhidaev — 2012-01-08T01:01:53

Hi!

I have the question about the proper gail and atk-bridge modules loading
for GTK+ application to enable their accessibility. At first orca
startup it asks usual questions and make some changes to enable GNOME
accessibility. On next GNOME launch at-spi2-registryd is present in
processes list but orca speaks only its greeting. The command "export
GTK_MODULES=gail:atk-bridge" before GTK-based application startup
(including orca itself) lets me enable proper accessibility  navigation
inside of this application but I don't know how these modules must be
loaded automatically for every application inside of GNOME
environment. Please, give me any  recommendation how I can debug this
problem!

Currently I have on my system libgtk+-3.2.3, at-spi2-core-2.2.3 and
orca-3.2.2. I am using ALT Linux distribution. It is not based on Debian
or Ubuntu packages so the problem can be caused by incorrect GNOME
components packaging.

Thanks!