Mike Gorse | 20 Aug 16:07 2014

ANNOUNCE: at-spi2-core 2.13.90 released

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


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.13.90

* Fixed a crash when using a collection match rule specifying
   interfaces (bgo#734805).

Where can I get more information about AT-SPI2

The project wiki is available at:


How can I contribute to AT-SPI2?

We need help testing with Gnome accessibility technologies, improving
(Continue reading)

Mike Gorse | 20 Jul 23:45 2014

ANNOUNCE: AT-SPI 2.13.4 released

AT-SPI 2.13.4 is now available for download at:


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.13.4

* [core] Ensure that we register with the session manager only once

* [core] Fix ucs2keysym prototype (bgo#730897).

* [core] introspection: add some missing Returns: (nullable) annotations

* [core] Fix various memory leaks.

* [atk] Fix typo in .pc file (bgo#721719).

* [atk] Fix retrieving text attributes (bgo#731980).

(Continue reading)

Nalin.x.Linux | 25 Jun 16:04 2014

Accessibility of ibus modules

Dear list,
I am Nalin from kerala/India, i am currently on the process of creating an ibus-engine for braille layout as part of google summer of code 2014 under the organisation swathanthra malayalam computing.It seems that orca screen reader is not announcing ibus-events such as expansion of preedit_string ,lookuptable etc. Currently we solved issue for ibus-sharada-braille engin using python-espeak api. Me with my mentor Samuel thibault discussed about this and we found various ways as follows

1 - make the ibus module speak by itself
2 - make the ibus module show a status bar where it writes what it wants to get spoken
3 - invent a new "input module" role, and events related to what an input module typically does (word expansion, word deletion, etc.)
4 - is there any way to register text event to at-spi via creating invisible accessible object ??

In this scenario please let us know what are the things we have to put forward to make ibus layouts accessible for screen reader users.
Expecting response nalin.

gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
Joseph Scheuhammer | 12 Jun 21:00 2014

Public working drafts release for WAI-ARIA 1.1

Two public working drafts of the WAI-ARIA 1.1 specification, and the 
Core Accessibility API Mappings were released earlier today (Jun 12, 2014):

Link to the W3C announcement:

Links to the documents:



'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
              - J. D. Klaun -
This Magpie | 8 May 11:12 2014


Hi List,

I would like to support the new java wrapper maintainer, Alejandro with the task of maintaining java-atk-wrapper since the whole module needs updating having been abandoned back in 2011[1]. 

The first commit since 2011, were just this week and, it's fair to say that the module has generally got a bit old and suboptimal over time.[2] I reckon it would really be great to put a bit more brainspace and time into improving things for java (by making use of what the most current java API can offer, for example). I won't have much time over the next 3 months but generally, I would like to have a go at helping get java-atk-wrapper up to scratch when I can, as long as that would not be a problem at all.

Does anybody have any thoughts about the module itself?

Many thanks,

gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
Patrick Welche | 19 Apr 18:52 2014

a11y bus trouble after upgrade

I have been upgrading eg dbus, glib, at-spi2-core etc. and now registryd
won't start. The best test so far, which is I think what
get_accessibility_bus_address_dbus() does in at-spi2-core atspi-misc.c is:

  dbus-send --print-reply --dest=org.a11y.Bus /org/a11y/bus \

which returns:

  Error org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.a11y.Bus exited with status 1

This suggests that the session bus is running sufficiently to accept a
connection, but then something fails - any clues on how to find out what?


Mike Gorse | 15 Apr 00:32 2014

ANNOUNCE: at-spi2-atk 2.12.1 released

At-spi2-atk 2.12.1 is now available for download at:


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-spi2-atk 2.12.1

* Clean up socket directories on exit (bgo#684076).

Where can I get more information about AT-SPI2

The project wiki is available at:


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:

Samuel Thibault | 3 Apr 00:10 2014

[Extended call] Accessibility and mobility topic of LSM 2014


The call for talks for LSM has been extended up to 15th April, please
consider submitting talks!


                 15th Libre Software Meeting
                      July 5-11, 2014
                     Montpellier, France
              Call For Papers and Participation
         limited to accessibility and mobility topic
     [we apologize for duplicate receipt of this message]
         Last call before deadline : april *15th* 2014

Sharing of knowledge, freedom of information, community spirit,
exchange of ideas, technological progress: every year the Libre
Software Meeting (LSM) follows the Libre philosophy.

RMLL/LSM is a non-commercial series of conferences, round tables
discussions and practical workshops based on Libre/Free Software and
its uses. Its aim is to provide a platform for Libre/Free Software
users, developers and stakeholders.

Access to LSM is free of charge and open to everyone. The conference
will be held in Montpellier from July 5 to July 11, 2014.

We hereby announce the opportunity to submit papers for selection by
the technical review committee for the RMLL/LSM 2014.

This year we would like to put a particular emphasis on accessibility
on the whole RMLL/LSM event. We will have our usual workshop, as
described below, but we would like to have accessibility talks held
in other sessions too, if possible all of them, as was achieved in
2010 in Bordeaux.  One of the reasons for that is that in France, on
1st January 2015, a law will enter in action to require accessibility
of all public places.  2014 is the last year to get ready for this.

We thus invite you to submit your accessibility talks to other topics
than the health topic, so as to broaden the audience of accessibility

Concerning our dedicated accessibility and mobility workshop,
to better target the various exchanges that will be taking place,
the programme committee of the accessibility and mobility 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

Information on workshops from last year is available on
- http://schedule2013.rmll.info/programme/sante/accessibilite-autonomie-et-gestion/

Information on the previous global RMLL/LSM emphasis on accessibility
in 2010 is available on
- http://2010.rmll.info/+-Accessibilite,2-+.html

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, ...),
... Conferences from last year are available on :
- http://schedule2013.rmll.info/

This year, LSM will have as guiding thread "Free software and you", which
can be particularly suited to the accessibility and mobility topic :)

If you are interested in participating, please submit your presentation

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. 

Deadlines =========

The following dates are important if you wish to participate to the
call for papers.

Abstract submission: no later than 15th of april 2014

Submission guidelines ====================

Speakers should submit an abstract in English or French ; about 400
words, and in 2 languages if possible. If accepted, this abstract
will be published on the website.

Submissions should be submitted via this form:

Submissions should also include the following:

  * Contact information and Geographical location of presenter
  (country of origin/passport).
  * A brief biography.
  * Any significant presentation and/or educational
  * For technical topics: Reason why this material is innovative,
  significant or an useful tutorial.
  * Optionally, any outlines or samples of prepared materials.
  * Information whether the submission has already been presented,
  and if so, where.

Personal information will be used exclusively for the sole purpose
of the RMLL/LSM committee and shall not be shared with third parties.

If the paper is not accepted for the main session, it may be accepted
for a short-form or "lightning talk" session.

Travel Assistance ====================

Non-commercial and based upon volunteer work, RMLL/LSM are events with
limited resources. However, speakers who exhibit particular need may
receive a refund for their transportation charges at the discretion
of the selection committee. If you know the estimated cost of the
transportation, providing this will make it easier for us to obtain
a clearer view of the expenses that will be incurred.

Publication on the web site ======================

The abstracts and slides for the conference will be published on
the event web site. The files should use only open formats and the
contents shall be shared under a free license.

Sponsoring ==========

If you wish to support the initiative and gain visibility by sponsoring
this event, please contact us by sending an e-mail to

Professionals, organisations and companies wishing to financially
support the RMLL/LSM can find more information on the website:

Web site =================

Event web site :


CfP website :


Best regards,
Programme Commitee of the LSM 2014 accessibility and mobility topic
John Emmas | 27 Mar 12:38 2014

Version 2 numbering

Hi guys,

I'm a bit confused about the "version 2" numbering for libatk.  I 
noticed this morning that a new branch got created for version 3 (the 
new branch is called "gnome-3-12") and I assume that it's timed to match 
similar libraries (such as glib / glibmm etc) who also just released 
version 3.12

However....  the latest atk branch I can find for version 2 is 
"gnome-2-30" - even though glib and glibmm are now 5 x releases further 
on, at ver 2.40.  Glib and Gtk seem to be developing versions 2 and 3 in 
parallel.  Is that not the case for atk or is there some other 
explanation for why the version 2 branches haven't moved on since 2.30?  
It's not a big problem.  I'm just curious to understand the difference.  

Magdalen Berns | 17 Jan 01:40 2014

GNOME Accessibility Mailing Lists

Hi lists,

Sorry for the cross post but this concerns both lists:

gnome-accessibility-devel [1]   

gnome-accessibility-list [2]

Both seem to be described as GNOME accessibility development or
technical discussion lists.

It does seem appropriate to provide a means for users to access support
from developers (and other users) but a bit less appropriate to subject
non-technical users to development threads in the process. So, it might
be a nice idea to:

a) move developer/technical discussion to gnome-accessibility-devel    

b) redefine gnome-accessibility-list as a list for users of the tools
and place to access support in using them instead of a development list.

What do people think about this?


[1] https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
[2] https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
magpie | 9 Jan 18:00 2014

[Fwd: Mousetweaks: integrate into GNOME Shell or keep in its current form?]

Happy 2014 everyone,

I thought I'd sent this last week but it came up in the a11y meeting 
today that the email was not in archives so I am resending and hopefully 
this finds everyone well. Further to that I am actually going to cross 
post to the GNOME Shell list (I was not sure whether to do that last 
week so did not) as Alejandro pointed out it is a decision for both 
mousetweaks developers and the GNOME Shell team to make so hopefully 
they will not mind the cross post! I added point 6 but have left the 
rest as it was.

I am bringing the following thread up:


It seemed to fizzle out with nothing decided and am hoping to finding 
out what people and hopefully Gerd and Francesco (the mousetweaks 
developers) are thinking now that some dialogue has happened. It would 
be good to find out what can be done for the feature. A few of 
points/questions/concerns on this:

1. I posted this out to both GNOME Shell and a11y lists first off 
(reluctant to keep doing that but feel free to forward this on anyone 
who thinks to do so) yet seems to have been very little comment from 
general group of gnome-shell developers. Will gnome-shell actually want 
this? I am less sure since I have tried quite a few times to get 
Mousetweaks in the menu for this 5 year old bug: 
https://bugzilla.gnome.org/show_bug.cgi?id=589906 and the response so 
far has not seemed very encouraging.

2. Component Maintenance in GNOME Shell. MouseTweaks into GNOME Shell 
might need to make sure that they (or someone at least) is going to be 
practically able to maintain and develop that work after it is in. Two 
reviews are needed for each commit, apparently. Getting one review seems 
pretty impossible, if two reviews are going to needed for bugs which 
arise after mousetweaks lands (assuming it would  there :-) ) Then g-s 
mousetweaks is probably going to have a difficult time keeping up.

3. Francesco seemed to have some reservations as I understood things I 
think he was concerned that implementing mouse-tweaks in gnome-shell 
would lead make Mousetweaks less accessible (i,e. by turning into a 
solution only gnome-users can access. If I got that right, and those 
concerns still exist then it would be good to discuss them a bit more so 
we can pinpoint what exactly might need to be done.

4. I pulled the extents logic rout of the magnifier and made it so the 
query to the component and text interfaces are done solely by the 
tracker, whatever client connects to it should be free to just make use 
of whatever extents it needs without the clients' developer having to 
rewrite existing code. This means mousetweaks should be able to easily 
make use of the focus tracking to perform the hover click actions by 
setting a threshold time and then performing some check to see whether 
an object is in focus long enough to activate a simulated click, I 
suppose. No doubt there is more to this, but I wonder will that help? If 
so I can polish that work off and file a bug for it.

5. GNOME Shell keyboard + mousetweaks. Thoughts?

6. If it does get written to GNOME Shell, would this be better as an 
extension rather than a component?

Best wishes,