http://permalink.gmane.org/gmane.comp.gnome.accessibility.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9185 <pre>Thanks a lot.. I will join this group and search more. On Tue, May 15, 2012 at 7:52 PM, Joanmarie Diggs &lt;jdiggs&lt; at &gt;igalia.com&gt; wrote: </pre> Udesh Liyanaarachchi 2012-05-15T14:49:00 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9184 <pre>Hey Udesh. From your description, I don't think Orca is relevant. Orca is a screen reader and presents things to users who are blind or visually impaired via speech output and/or refreshable braille. Have you connected with the Simon project? Project page: http://www.simon-listens.org KDE A11y list: https://mail.kde.org/mailman/listinfo/kde-accessibility Hope this helps. Take care. --joanie On 05/14/2012 08:40 PM, Udesh Liyanaarachchi wrote: </pre> Joanmarie Diggs 2012-05-15T14:22:54 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9183 <pre>Great work..!! Hope I can get a help from Orca to my GSoc project adding voice control for Banshee http://tecstuf.blogspot.com/ Any suggestion would be so helpful. Thanks &amp; Regards, On Tue, May 15, 2012 at 6:03 AM, Luke Yelavich &lt;themuso&lt; at &gt;ubuntu.com&gt; wrote: </pre> Udesh Liyanaarachchi 2012-05-15T00:40:47 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9182 <pre> I am in the process of preparing it for Ubuntu's proposed updates repository, and I'll put out a call for testing when its available. Luke </pre> Luke Yelavich 2012-05-15T00:33:12 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9181 <pre>Taht si great news! Will this come in Ubuntu's updates, or will I need to get it from Git? Hope all is well, and thanks for all of the hard work. On 05/14/2012 03:29 PM, Joanmarie Diggs wrote: </pre> Robert Cole 2012-05-14T23:21:08 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9180 <pre>============= What is Orca? ============= Orca is a free, open source, flexible, and extensible screen reader that provides access to the graphical desktop via user-customizable combinations of speech and refreshable braille. You can read more about Orca at http://live.gnome.org/Orca. ========================= What's Changed in 3.4.2? ========================= General * Fix for bug 675522 - incorrect comment for translators * Prevent gnome-shell notifications from being double-presented * Try to handle metacity timeouts more gracefully * Fix for bug 674237 - More unicode errors found with hungarian locale * Fix for bug 674693 - Modifier keys pressed alone should interrupt speech * Prevent Orca from interrupting speech in Anaconda trees Where can I get it? =================== http://download.gnome.org/sources/orca/3.4/orca-3.4.2.tar.xz Enjoy! </pre> Joanmarie Diggs 2012-05-14T22:29:43 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9179 <pre>Dear reader, A new release of mousetweaks is available; the version number is 3.4.2. It can be downloaded from: http://download.gnome.org/sources/mousetweaks/3.4/ Direct download link: http://download.gnome.org/sources/mousetweaks/3.4/mousetweaks-3.4.2.tar.xz (1.94M) sha256sum: 7f8a6ae627edae12e0d5b92926c33191bfa504c1ccaf51195051681aedfa700c ===================== What is mousetweaks ? ===================== Mousetweaks is a package that provides mouse accessibility enhancements for the GNOME desktop. These enhancements are: 1. It offers a way to perform the various clicks without using any hardware button. (Hover Click) 2. It allows users to perform a secondary click by keeping the primary mousebutton pressed for a determined amount of time. (Simulated Secondary Click) These enhancements can be accessed through the Universal Access panel in the GNOME Control Center or through the command-line interface. =================== Distribution Notes: ===</pre> Francesco Fumanti 2012-05-14T19:50:06 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9178 <pre> And I've been at a conference this week, so was delayed responding myself. I hope you don't mind that I've taken the liberty of cc'ing the X.Org development list so the developers working on the input handling in X (and even some of the ones working on the input handling in Wayland) can see and respond to these issues. I think the two went hand in hand - it wasn't being maintained because it wasn't seen as generally needed. Like GNOME, X.Org development is done either by employees of corporations meeting their corporate needs (in X's case, mostly OS/distro vendors or graphics/input device vendors) or volunteers working on the parts that personally interest them or meet their needs. And as noted in the mail of mine from 2010, there was some thought that the more general solutions in later Xinput releases could be used instead of the special purpose solution in XEvIE. Unfortunately, I'm not deeply enough involved in the input side to know what the answers are here - I'm just trying to provide a cataly</pre> Alan Coopersmith 2012-05-12T03:46:46 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9177 <pre>Hey all. * Reminder: 2012/05/10 16:00 CET a11y weekly meeting * Agenda-in-progress: http://live.gnome.org/Accessibility/Meetings * Reminder: Add your agenda items prior to the meeting * Subscribe-able Team Calendar: http://bit.ly/GNOME-A11y-Calendar Be there or be square! ;) --joanie </pre> Joanmarie Diggs 2012-05-10T02:14:49 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9176 <pre>Hi Alan, thanks for your mail, and sorry for the delay in my answer, I have been doing some research. On 05/07/2012 04:22 PM, Alan Coopersmith wrote: Well, I was not here when XEvIE was born or was let to die, so probably the info that I have is incomplete. As I was told, XEvIE was not let die because nobody required it, but because was maintainerless. In fact, Daniel Stone mentioned that was somewhat broken since day 1 (see his comment at the end of my post here [2]). Googling a little, I found this interesting mail [4] (also written by you). And it seems that main consumer of XEvIE was gok (in fact, AFAIK, just one app could use XEvIE at the same time, so at-spi was being used as a kind of wrapper). Register to global key events on ATK based on server-side key snooping was added since the beginning at 2001. XEvIE support on at-spi was added on 2003, and mainly to be used by gok. So I assume (please see my previous "probably the info that I have is incomplete", correct me if I'm wrong), that the problem </pre> Piñeiro 2012-05-08T12:10:56 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9175 <pre> BTW, from the X.Org developer point of view, one of the reasons we let XEvIE die was because it didn't seem like anyone required it, or even really noticed that it had been broken for a couple releases before the removal. If there are requirements from X or Wayland that are going unmet, step 1 is letting the developers of those systems know. </pre> Alan Coopersmith 2012-05-07T14:22:59 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9174 <pre>Hi Jason, On 05/07/2012 04:58 AM, Jason White wrote: As far as I know, no. At least no Wayland developer provided any feedback on gnome-accessibility, gnu-accessibility or any other of the accessibility-related mailing lists I'm subscribed to. Anyway, we have Wayland in consideration. Some historic context: We had a brief thread about this on 2010. It started on gnome-accessibility-list: https://mail.gnome.org/archives/gnome-accessibility-list/2010-November/msg00054.html Although it also touched gnome-shell mailing lists. https://mail.gnome.org/archives/gnome-shell-list/2010-November/msg00040.html Due this conversation, we include Wayland as one of the things to talk about in the first ATK/AT-SPI2 hackfest, and we created a bug to track it: https://bugzilla.gnome.org/show_bug.cgi?id=649556 But the conclusions of the Hackfest didn't provide too much light: https://bugzilla.gnome.org/show_bug.cgi?id=649556#c1 So we know basic things, like that we want X/Wayland totally transparent to ATK, and that pro</pre> Piñeiro 2012-05-07T10:35:51 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9173 <pre>Are there people with backgrounds in accessibility development working with the Wayland project? In particular, the accessibility infrastructure will need to be fully supported on systems that run Wayland without an X server. The latest Wayland update that I've read mentions keyboard handling as one of the aspects of Wayland development that is still in flux, hence there may be opportunities for those who understand the requirements of AT-SPI 2, Orca etc. in this area to make their requirements known before the relevant APIs are set. http://lwn.net/Articles/491509/ I know that it will remain possible to run X as a Wayland client, but, given the current thinking of X and Wayland developers, the norm will be for desktop environments to use Wayland directly without an X server. </pre> Jason White 2012-05-07T02:58:33 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9172 <pre>Hey all. As discussed during last week's team meeting, Shaun is organizing the Open Help Conference [1] and would like our input. I have created a "brainstorming" page on our wiki [2] so folks can jot down ideas. Please add your thoughts. Thanks and take care. --joanie [1] http://http//openhelpconference.com [2] http://live.gnome.org/Accessibility/AccessibleHelp </pre> Joanmarie Diggs 2012-05-03T15:06:53 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9171 <pre>Hey all. * Reminder: 2012/05/03 16:00 CET a11y weekly meeting * Agenda-in-progress: http://live.gnome.org/Accessibility/Meetings * Reminder: Add your agenda items prior to the meeting * Subscribe-able Team Calendar: http://bit.ly/GNOME-A11y-Calendar Be there or be square! ;) --joanie </pre> Joanmarie Diggs 2012-05-03T03:10:48 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9170 <pre>============= What is Orca? ============= Orca is a free, open source, flexible, and extensible screen reader that provides access to the graphical desktop via user-customizable combinations of speech and refreshable braille. You can read more about Orca at http://live.gnome.org/Orca. ========================= What's Changed in 3.5.1? ========================= News ==== General * Prevent gnome-shell notifications from being double-presented * Try to handle metacity timeouts more gracefully * Fix for bug 674237 - More unicode errors found with hungarian locale * Fix for bug 674693 - Modifier keys pressed alone should interrupt speech * Prevent Orca from interrupting speech in Anaconda trees New and updated translations (THANKS EVERYONE!!!): cs Czech Marek Černocký gl Galician Fran Diéguez nb Norwegian bokmål Kjartan Maraas sl Slovenian Matej Urbančič te T</pre> Joanmarie Diggs 2012-04-30T23:23:00 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9168 <pre>Hey all. * Reminder: 2012/04/25 16:00 CET a11y weekly meeting * Agenda-in-progress: http://live.gnome.org/Accessibility/Meetings * Reminder: Add your agenda items prior to the meeting * Subscribe-able Team Calendar: http://bit.ly/GNOME-A11y-Calendar Be there or be square! ;) --joanie </pre> Joanmarie Diggs 2012-04-25T20:44:50 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9167 <pre>Hey all. * Reminder: 2012/04/19 16:00 CET a11y weekly meeting * Agenda-in-progress: http://live.gnome.org/Accessibility/Meetings * Reminder: Add your agenda items prior to the meeting * Subscribe-able Team Calendar: http://bit.ly/GNOME-A11y-Calendar Be there or be square! ;) --joanie </pre> Joanmarie Diggs 2012-04-18T14:53:10 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9166 <pre>Hey Jason. I agree. On a related note, check out the LibreOffice Navigator. It already does in LibreOffice what is being proposed for addition in Orca. And it does so incredibly performantly, without a need to examine the entire accessible tree, and can be used by everyone. Bonus points that I don't have to maintain that code, update that code (e.g. to Python 3 which is on this cycle's to-do list, or gobject introspection like a couple of cycles ago). Nor do I have to debug that code with LibreOffice decides to toss yet another dead accessible in our general direction. If the Navigator is lacking a particular element, I think the thing to do is add that missing element to the LibreOffice Navigator and improve the feature for everyone. I also wish that the energies spent in trying to add yet one more thing into Orca would instead be spent on trying to improve the applications Orca users wish to access. That might be enhancing the LibreOffice Navigator code or fixing LibreOffice accessibility bugs. Or, if</pre> Joanmarie Diggs 2012-04-17T21:49:41 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9165 <pre>Hi Dattatray, In addition to Jason's comments below, I'd like to weigh in from a historical perspective... Many years ago, we decided to only expose Accessibles for the visible content in OOo because of the huge memory hit doing otherwise would involve for a large document. For this reason we worked on an AccessibleDocument interface as a way to iterate over large content like in Writer. I don't recall the more recent history relating to implementing that interface there. At this point, I suspect Jason's recommendations are the better route; or to explicitly special case Writer and use the Writer/UNO APIs for getting this information directly. Regards, Peter On 4/17/2012 12:26 AM, Jason White wrote: </pre> Peter Korn 2012-04-17T17:29:18 http://permalink.gmane.org/gmane.comp.gnome.accessibility.general/9164 <pre> At this point, what we need is the "I'm in!" factor. So far, I'm seeing marketing folks respond to this, and that's great, but we really want to be careful not to make this look like a purely marketing effort. People out there are interested in a11y, but need more indepth information on the technical side. I guess the next step we can do while waiting for more technical guru "I'm in!"'s is to collaborate on the list of people/orgs to ping. Karen, you and I could work together on this. I'd like to try to at least get some level of direction that we'll be moving forth on this before I reach out to OLF. Now is good time to work with OLF because they're still in the early planning stages of their event. Bryen </pre> Bryen M Yunashko 2012-04-17T14:54:18 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.accessibility.general