http://blog.gmane.org/gmane.comp.gnome.accessibility.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3801 <pre>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 </pre> Mike Gorse 2012-04-30T21:39:43 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3794 <pre>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 &lt;API&gt; #action Piñeiro after some researching, will bring the having accessibility by default 3.6 to the accessibility list Apr 19 16:10:32 &lt;API&gt; #action Piñeiro after some debate we could propose it as feature So after that research I'm here to talk about this (output</pre> Piñeiro 2012-04-20T16:15:13 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3790 <pre>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? ===============</pre> Mike Gorse 2012-04-16T19:37:44 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3786 <pre>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-&gt;callback (atspi_event_copy (e), entry-&gt;user_dat</pre> Patrick Welche 2012-04-05T11:17:04 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3785 <pre>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 per</pre> Mike Gorse 2012-03-26T21:05:20 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3784 <pre>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 disa</pre> Piñeiro 2012-03-26T18:59:31 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3783 <pre>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 =========================</pre> Mike Gorse 2012-03-20T21:00:37 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3782 <pre>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 disa</pre> Piñeiro 2012-03-19T23:36:49 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3779 <pre>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 disa</pre> Piñeiro 2012-03-07T12:40:30 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3778 <pre>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: &lt;p contentEditable="true" aria-disabled="true"&gt; Currently: no enabled state, no editable state. This paragraph exposed absolutely identically to plain &lt;p&gt;. Proposed: no enabled state, editable state is presented. AT understand this paragraph is sort of control and can be used for typing when enabled. </pre> Alexander Surkov 2012-03-07T06:45:52 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3777 <pre>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. * [co</pre> Mike Gorse 2012-03-06T00:44:02 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3776 <pre>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 disa</pre> Piñeiro 2012-03-06T00:32:22 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3775 <pre>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 &amp; 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 &amp; accessibility workshop is held as part of this broader meeting. This year, it </pre> Samuel Thibault 2012-03-01T01:27:58 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3774 <pre>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) </pre> Patrick Welche 2012-02-23T18:56:26 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3773 <pre>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 </pre> Mike Gorse 2012-02-20T23:45:51 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3771 <pre>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</pre> Mike Gorse 2012-02-07T04:57:29 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3764 <pre>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</pre> Mike Gorse 2012-01-16T03:57:01 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3760 <pre>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 </pre> Smitten 2012-01-13T20:30:53 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3749 <pre>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! </pre> Michael Pozhidaev 2012-01-08T01:01:53 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3747 <pre> 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&lt; at &gt;gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel </pre> Benjamin Hawkes-Lewis 2012-01-07T18:09:30 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3749 <pre>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! </pre> Michael Pozhidaev 2012-01-08T01:01:53 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.accessibility.devel