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/3873 <pre>Hey folks, In light of the gradual move to wayland, I am wondering what the plans are WRT at-spi, specifically, dealing with keyboard snooping and Wayland input. Last I heard from Alejandro, nothing was set in stone WRT wayland and input related APIs for snooping. As you probably know, Canonical has decided to write its own display server, Mir.(1) From what I understand, parts of it will be similar to Wayland, but I am not sure whether that will be the case for input APIs. Either way, I will have to start working on this once I have something from our Mir devs to work with, so I was hoping that code could be shared, so far as the backend of the at-spi registry daemon is concerned. Thanks, Luke </pre> Luke Yelavich 2013-04-25T00:16:08 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3867 <pre>Hey all. As many of us know, AtkText is one thorough interface. :) So thorough, in fact, that it boggles the minds of those implementing it and sends many others running to create PangoLayout instances so that they can use GailTextUtil to do the implementation for them. So I am here to propose we simplify AtkText and do it *now* i.e. while we are very early in the GNOME cycle. In particular, I would like to suggest for your consideration the following two changes: 1. Deprecate atk_text_get_text_{before,after}_offset() 2. Deprecate the TEXT_BOUNDARY_FOO_{START,END} In the first case, clients such as Orca would use (through AT-SPI2) atk_text_get_text_at_offset(). If the text before or after a given offset were desired, clients would make a second call having gotten the needed offset from the first call. In the second case, clients such as Orca would use (through AT-SPI2) a brand new set of TEXT_BOUNDARY_FOO boundaries. My guess is that we'd want it to mimic the behavior of the current START results, but t</pre> Joanmarie Diggs 2013-04-13T19:09:53 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3866 <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. News ==== * * Updated Visual C++ configuration files * Make entries more consistent with the other GNOME Visual Studio projects. * Enable the building of introspection files for Visual C++ bu</pre> Piñeiro 2013-03-26T11:05:36 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3865 <pre>AT-SPI 2.7.91 is now available for download at: http://download.gnome.org/sources/at-spi2-core/2.7/ http://download.gnome.org/sources/at-spi2-atk/2.7/ http://download.gnome.org/sources/pyatspi/2.7/ 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.7.91 * Add method to retrieve the locale o an accessible (BGO#694368). * [core] Launch at-spi-bus-launcher in initialization phase (BGO#694984). * [pyatspi] Stop using a deprecated method. * [pyatspi] Don't install sample, as it is not compatible with Python 3. Where can I get more information about AT-SPI2 ============================================== The project wiki is available at: http://ww</pre> Mike Gorse 2013-03-04T22:53:18 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3861 <pre>Hey folks, I've been playing with QT 5 lately, testing out accessibility, and so far thigs look pretty good. One thing I've noticed is that I cannot use Orca flat review in Qt apps, which was also the case with Qt 4. So I've set about trying to work out why this is. I initially thought it was due to Orca not having a script to work with Qt apps, i.e a toolscript similar to the cally and gail scripts, but I figured there was more to it than that. So far, I've come to the conclusion that the app toolkit in use, i.e GTK has to implement some form of key snooping to catch the appropriate keystrokes and send them to atk/at-spi. Of course I may be missing part or all of the puzzle. So to be clear, I would appreciate an explanation as to how the key snooping and key event trapping for Orca keystrokes works. If it is indeed Qt that needs to implement something to make this work properly, then a good explanation may help either Frederick or someone else in doing whats needed to get Orca properly working with Qt apps</pre> Luke Yelavich 2013-02-20T18:24:54 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3858 <pre>AT-SPI 2.7.90 is now available for download at: http://download.gnome.org/sources/at-spi2-core/2.7/ http://download.gnome.org/sources/at-spi2-atk/2.7/ http://download.gnome.org/sources/pyatspi/2.7/ 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.7.90 * [core] Removed a debug print that was accidentally included in 2.7.5. * [atk] Bump atk dependency to 2.7.5 (BGO#693189). 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 tech</pre> Mike Gorse 2013-02-18T23:00:11 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3850 <pre>Hi guys, please help me with this. I just need a recommendation on the direction to take. my case: I need to develop a desktop application for linux fedora or ubuntu (or any of their derivatives). I prefer it to work on gnome, but KDE is also ok. My application is not big, it is just a tool to read some RSS feeds. And it must be compatible with screen readers available for linux, like ORCA. If possible I want it to be cross-platform: windows, mac and linux. my attempts so far: I tried QT version 5. Accessibility ok in windows, but on linux it does not work.... it even makes ORCA crash. Which is sad because QT looks very interesting. Then I tried java swing. Accessibility works nice and easy on Windows and Mac, but on linux I got stuck trying to compile ATK or the java access bridge, I even tried installing the binaries but still Accessibility of a java swing window just does not work for me on linux.... will try a little more. My next options are: Try with GTK+. Try with wxPython. So, any tips or reco</pre> Taksan 2013-01-22T17:51:42 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3849 <pre>Hi, this is the announcement of a new release of Caribou. This is a unstable release towards Gnome 3.8. Please test this new release, it has several changes. Feedback is welcome. Caribou is a screen keyboard and a library for other screen keyboards. News =============== - Bug 687244: Add documentation support - Bug 687315: various packaging fixes: - build: only export public symbols from the library - build: make sure to define $datarootdir in generated scripts - build: suppress Python bytecode generation when building - build: install vapi file - build: install pkg-config file - build: use git.mk - build: don't use deprecated Automake variable INCLUDE - build: rename caribou.pc to caribou-1.0.pc - Bug 691463: libcaribou: avoid integer overflow - Fix 'make install' when --enable-docs is used - Translation updates (Friulian) Contributors ============ Alejandro Piñeiro Iglesias, Daiki Ueno Translations ============ TmTFx (fur) Download ======== http://download.gnome.org/sources/caribo</pre> Piñeiro 2013-01-15T19:29:22 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3848 <pre>I've just rolled a new tarball for at-spi2-core to fix a major crasher that made its way into 2.7.4. ftp://ftp.gnome.org/pub/gnome/sources/at-spi2-core/2.7/at-spi2-core-2.7.4.1.tar.xz -Mike </pre> Mike Gorse 2013-01-15T17:09:18 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3847 <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. News ==== * Bug 690379: Atk lacks any kind of version utilities * Fixed out of tree builds caused by fix of bug 690379 * Bug 656750: AtkWindow requires documentation Contributors ============ Emmanu</pre> Piñeiro 2013-01-15T11:11:51 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3844 <pre>Hi, this is the announcement of a new release of Caribou. This is a unstable release towards Gnome 3.8. Please test this new release, it has several changes. Feedback is welcome. Caribou is a screen keyboard and a library for other screen keyboards. News =============== - Bug 688517: libcaribou: refactor some code - Bug 688656: key-model: Use key-released instead of key-clicked to hide subkeys - Bug 689823: caribou-preferences: Fix expansion of LD_LIBRARY_PATH - Translation updates (Aragonese) Contributors ============ Daiki Ueno, Colin Walters Translations ============ Jorge Pérez Pérez (an) Download ======== http://ftp.gnome.org/pub/GNOME/sources/caribou/0.4/caribou-0.4.6.tar.xz </pre> Piñeiro 2012-12-17T19:42:48 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3843 <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. News ==== * Bug 689907: Problems with the management of * ATK_STATE_SELECTABLE/ATK_STATE_SELECTED states at AtkObject * Bug 686746: Port introspection fixes from Vala * Bug 689952: Add introspection</pre> Piñeiro 2012-12-17T19:06:58 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3842 <pre>Hi, this is the announcement of a new release of Caribou. This is a unstable release towards Gnome 3.8. Please test this new release, it has several changes. Feedback is welcome. Caribou is a screen keyboard and a library for other screen keyboards. News =============== - Bug 687018: xadapter: use level3 shift if possible - Bug 673547: xadapter: use XkbChangeMap instead of XkbSetMap - Bug 673547: xadapter: specify core device when callin XkbSetMap - Bug 685629: portability: use "=" operator instead of "==" in shell scripts - portability: allow the use of /bin/sh instead of /bin/bash - Bug 685607: libcaribou: simplify using xtst.vapi provided by vala - Bug 673579: libcaribou: Ignore level 3 keysyms when looking up keycode - Bug 687026: xml: add "text" attribute to key - Bug 685792: daemon: use GDBUS directly instead of dbus-python - Bug 686200: make_schema: don't translate string in schema files - Bug 687409: Fix border-image slice values in antler's gtk CSS - Bug 687166: Port from libgee 0.6 to 0.8 - B</pre> Piñeiro 2012-11-20T18:21:52 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3841 <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. News ==== * Bug 686801: Extend atk_add_global_event_listener in order to support signal details Contributors ============ Alejandro Piñeiro Translators =========== Theppitak Karoonboonyanan (th)</pre> Piñeiro 2012-11-20T18:08:30 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3842 <pre>Hi, this is the announcement of a new release of Caribou. This is a unstable release towards Gnome 3.8. Please test this new release, it has several changes. Feedback is welcome. Caribou is a screen keyboard and a library for other screen keyboards. News =============== - Bug 687018: xadapter: use level3 shift if possible - Bug 673547: xadapter: use XkbChangeMap instead of XkbSetMap - Bug 673547: xadapter: specify core device when callin XkbSetMap - Bug 685629: portability: use "=" operator instead of "==" in shell scripts - portability: allow the use of /bin/sh instead of /bin/bash - Bug 685607: libcaribou: simplify using xtst.vapi provided by vala - Bug 673579: libcaribou: Ignore level 3 keysyms when looking up keycode - Bug 687026: xml: add "text" attribute to key - Bug 685792: daemon: use GDBUS directly instead of dbus-python - Bug 686200: make_schema: don't translate string in schema files - Bug 687409: Fix border-image slice values in antler's gtk CSS - Bug 687166: Port from libgee 0.6 to 0.8 - B</pre> Piñeiro 2012-11-20T18:21:52 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3841 <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. News ==== * Bug 686801: Extend atk_add_global_event_listener in order to support signal details Contributors ============ Alejandro Piñeiro Translators =========== Theppitak Karoonboonyanan (th)</pre> Piñeiro 2012-11-20T18:08:30 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3838 <pre>Background: I was setting up a GNOME 3.6.1 demo machine, and was in the process of verifying that the interim magnifier focus tracker was working properly, when I came across the following. Focus tracking did *not* function as expected in FireFox nor LibreOffice. Tracking the keyboard focus did not occur with these applications. By comparison, gnome-shell widgets (e.g., menus, task switcher) all worked as expected in terms of focus tracking. Another clue: I went on to check the Orca set up, launching it, and later quitting. Then I went back to look further into the focus tracking issues with FireFox and LibreOffice. To my surprise focus tracking now worked with these apps as well. We discussed this at last week's gnome-a11y meeting, noting that in gnome 3.6 a11y is "always on". Furthermore, gnome-shell respects that. We hypothesized that FF and LO do not, and require some further push to engage accessibility. </pre> Joseph Scheuhammer 2012-11-12T20:12:11 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3837 <pre>Hi, this is the announcement of a new release of Caribou. This is a stable release for gnome-3-6. So the reason it is 0.4.4.2 instead of 0.4.6. It doesn't include all the changes made at master. It is just 0.4.4 with just some critical patches included. Caribou is a screen keyboard and a library for other screen keyboards. NEW =============== Version 0.4.4.2 =============== - Bug 685792: use GDBus directly instead of dbus-python - Bug 685629: use "=" operator instead of "==" in shell scripts - 687409: Fix border-image slice values in antler's gtk CSS Thanks ===== Daiki Ueno Download ====== http://ftp.gnome.org/pub/GNOME/sources/caribou/0.4/caribou-0.4.4.2.tar.xz </pre> Piñeiro 2012-11-12T18:59:20 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3833 <pre>AT-SPI 2.7.1 is now available for download at: http://download.gnome.org/sources/at-spi2-core/2.7/ http://download.gnome.org/sources/at-spi2-atk/2.7/ http://download.gnome.org/sources/pyatspi/2.7/ 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.7.1 * [core] Update the cache in response to role change notifications (BGO#685469). * [core] Don't output a warning when a p2p connection isn't available. * [atk] Remove the schema; it was only used to specify the location of the atk-bridge library, which is now installed in the standard path. * [atk] Fix compiler warnings (BGO#678045). * [pyatspi] Export application class in the Accessibility na</pre> Mike Gorse 2012-10-22T17:11:23 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3829 <pre>It's probably too late to do anything about this. The version of pyatspi-2 on the "try it out" live iso for GNOME 3.6 is 2.5.92. I assume it should be 2.6.0, since that's the latest release? I've checked these two images: ftp://ftp.gnome.org/pub/gnome/misc/promo-usb/GNOME-3.6.0.iso http://ftp.gnome.org/pub/gnome/misc/testing/GNOME-3.6.0.iso </pre> Joseph Scheuhammer 2012-10-02T20:52:11 http://comments.gmane.org/gmane.comp.gnome.accessibility.devel/3826 <pre>AT-SPI 2.6.0 is now available for download at: http://download.gnome.org/sources/at-spi2-core/2.6/ http://download.gnome.org/sources/at-spi2-atk/2.6/ http://download.gnome.org/sources/pyatspi/2.6/ 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.6.0 * [atk] Fix some crashes in atk_bridge_adaptor_cleanup (BGO#684434). * [atk] When the cache is activated, register it on the main D-Bus connection. * [pyatspi] Install caret focus tracker into $bindir, rather than $pythondir/examples. * [pyatspi] Fix incorrect FSF address in file headers. Where can I get more information about AT-SPI2 ============================================== The projec</pre> Mike Gorse 2012-09-24T22:17:03 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.accessibility.devel