Mike Gorse | 30 Apr 23:39
Favicon

ANNOUNCE: AT-SPI 2.5.1 released

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
(Continue reading)

Piñeiro | 20 Apr 18:15
Favicon

About proposing "accessibility on by default" as feature

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
(Continue reading)

Mike Gorse | 16 Apr 21:37
Favicon

ANNOUNCE: at-spi2-core 2.4.1 released

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?
(Continue reading)

Patrick Welche | 5 Apr 13:17
Picon
Picon
Favicon

at-spi2 and a11ytesting core dump

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, 
(Continue reading)

Mike Gorse | 26 Mar 23:05
Favicon

ANNOUNCE: AT-SPI 2.4.0 released

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?
(Continue reading)

Piñeiro | 26 Mar 20:59
Favicon

ATK 2.4.0 released

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
====

(Continue reading)

Mike Gorse | 20 Mar 22:00
Favicon

ANNOUNCE: AT-SPI 2.3.92 released

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
==============================================

(Continue reading)

Piñeiro | 20 Mar 00:36
Favicon

ATK 2.3.95 released

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
====

(Continue reading)

Piñeiro | 7 Mar 13:40
Favicon

ATK 2.3.93 released

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
====

(Continue reading)

Alexander Surkov | 7 Mar 07:45
Picon

ATK STATE_EDITABLE

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
Mike Gorse | 6 Mar 01:44
Favicon

ANNOUNCE: AT-SPI 2.3.91 released

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
(Continue reading)


Gmane