http://blog.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/506 <pre>This is 4.0.3-rc3 from the Debian package. To reproduce: 1. Create or load a sample document in LO Writer. 2. Ctrl-Shift-s to select "save as". 3. Change the file name appropriately and the format to, for example plain text. 4. Select "save". At this point the crash occurs, with the following errors: Can others reproduce this? Does it only occur with accessibility active or is it a general issue? I can't test without accessibility and Orca operating. Script started on Wed 08 May 2013 13:04:22 EST jason&lt; at &gt;jdc:~$ loffice /tmp/test-document.html ** (soffice:13163): WARNING **: Unknown type: GailWindow (soffice:13163): GLib-GObject-WARNING **: invalid cast from `GtkAdjustment' to `GtkWindow' (soffice:13163): GLib-GObject-WARNING **: invalid cast from `GtkAdjustment' to `GtkWidget' (soffice:13163): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:2459: signal `focus-out-event' is invalid for instance `0x2904400' (soffice:13163): GLib-GObject-WARNING **: invalid cast</pre> Jason White 2013-05-08T03:27:22 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/502 <pre>Hello, sorry for spamming all the lists, but in the light of recent events and discussions, I'd like to make all of you aware of an important mailing list, that so far has not been used as extensively as it should be, which led to some frustration and communication issues. As part of our mission to foster the project internal communication, I'd like to tell you about our so called projects mailing list, which Sophie initiated quite a while ago, and which should be used for communication amongst the various projects - e.g. design and marketing, development and marketing, UX and development, and the like. The list's intention is not to be a gossip list where everything should be thrown at, but to make all affected projects aware of important changes. Philosophy: Low traffic, but important topics. Some examples are: Change of version numbers, a new slogan, design changes, new products. In other words: Everything that has an impact on other areas of working than the one where the change originally</pre> Florian Effenberger 2013-05-04T13:24:57 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/501 <pre>Hello, at the moment, we are looking for volunteers who could help moderate this mailing list. If you are interested, the only requirement is that you are subscribed to the list yourself and read its mails in a somehow timely manner, but that's about it. Moderation means dealing with e-mails that do not automatically make it to the list, which you then manually forward, or reject. This happens either when an e-mail comes from an unknown sender, e.g. when a project member uses a different address for posting. It also occurs when someone unexperienced writes to the list, thinking it's a private account, but in fact it's a public list. You'll receive the message to be moderated via e-mail, which you then can either "moderate through", or reject. Is someone interested in joining our efforts? It'd be much appreciated - just drop me an email (please also copy me directly, and not only the list), then I'm happy to add you to the list of moderators. Thanks! Florian </pre> Florian Effenberger 2013-05-04T11:22:33 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/499 <pre>Hi Tom, No it was an issue with the 4.1.0 daily builds of master. The bug listed, fdo#63680, deals with indeterminant crashes of Writer on Windows builds of master--the last viable TinderBox build occurred 8 April, so this issue has been on the Most Annoying Bugs list for the 4.1 development. Also, turned out to be a problem over on the NV Access, NVDA side where one of the modules for handling Java Access Bridge based content was misconfigured in their upcomming 2013.1 release as compared to the stable 2012.3.1 version--that has been corrected. With the TDF and LibreOffice with 3.6.7, 4.0.3 and ongoing development of master (currently notated 4.1.0+ alpha) I cycle through all the branches testing for Windows (and occasionally Linux and OSX builds) looking at general usability and trying to identify accessibility issues. At any time I will have 4 or 5 LibreOffice or Apache OpenOffice installations and assistive technologies loaded. Not too difficult to accomplish, just have to pay attention to configura</pre> V Stuart Foote 2013-04-23T10:31:29 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/497 <pre>On Windows 7 SP1 64-bit JRE 1.6.45 JAB 2.0.2 Bumped into a an issue with Java Access Bridge and LibreOffice today's Master daily build. When running the NVDA 2012.3.1 AT screen reader, a long stable test document is crashing LibreOffice 4.1 alpha from Master when accessed with NVDA AT in use. Without NVDA AT active, the document opens fully in todays daily build. Without NVDA AT activated, the JavaFerret and JavaMonkey utilities both show the document opening correctly with today's LibreOffice build of Master. And on the same system, earlier builds of Master, 4.0.3.1 and 4.0.2.2 opened and continue to open while NVDA is in use. Have opened an issue with NVAccess against NVDA 2012.3.1 ( http://community.nvda-project.org/ticket/3170 ) but suspect it could be recent Java work in LibreOffice--Java Ferret/Java Monkey less sensitive to whatever the issue is. Test document opens with these builds of LibreOffice while NVDA is active LibreOffice_4.0.2_Win_x86.msi LibreOffice_4.0.3.1_Win_x86.msi (administrati</pre> V Stuart Foote 2013-04-18T21:36:39 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/495 <pre>Software like Lingdys and Lingright from http://lingit.no/ are unable to work with 4.x. Torbjørn Norgård &lt;torbjorn&lt; at &gt;lingit.no&gt; told me that no text sequences or pressed keys can be extracted and thus the software are unable to assist the user. I know that some older accessibility API's etc was removed, but could someone shed some more light on this subject? </pre> Olav Dahlum 2013-04-12T12:15:02 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/492 <pre>Hello every one, I have just been on the list for a few days and as of yet I have seen no traffic, so, I am guessing that this is a low traffic list and that is a good thing. I am Keith Reedy director of Bibles for the Blind in the US, www.biblesfortheblind.org We have just begun to use LibreOffice with the ODT to Braille extension to translate print documents in to braille. I would like to talk with some one who is using LibreOffice in the same manner about a couple of things I have found to see if some one has found a workaround. I am using an iMac with OS 10.8 and we do have a couple of 10.6 iMacs on site as well. Thanks. Keith Reedy keithreedy&lt; at &gt;fastmail.net </pre> Keith Reedy 2013-04-09T15:04:55 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/488 <pre>fdo#61468 was added to mab 4.0, but it needed to be combined with fdo#61389. So used the earlier report on the MAB list. Cross posting this to the UX list because while the the new (at 4.0.0) Template Manager is a a really great feature, it somehow made it through development and QA deficient in its accessibility roles. I hope all can agree that for effective AT, accessibility roles and interfaces really benefit from consistency and a fully instrumented accessibility structure. With so many development channels, it is not clear to me how to achieve that earlier in the component and feature design, But looking at the new Template Manager, in context with long standing accessibility issues with the F11 - Styles &amp; Formatting panel, it is clear that some renewed UX team emphasis on accessibility and support for AT in the user interface is needed. Stuart </pre> V Stuart Foote 2013-03-02T21:46:51 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/487 <pre>This has been filed as LibreOffice bug fdo#61390 - https://bugs.freedesktop.org/show_bug.cgi?id=61390 and the DEVs of template manager notified. Stuart ________________________________________ From: ktc [regx&lt; at &gt;c-net.us] Sent: Friday, March 01, 2013 9:38 AM To: accessibility&lt; at &gt;global.libreoffice.org Subject: [libreoffice-accessibility] keyboard accessibility of new template manager Is it on anyone's radar to make the LO 4.x template manager keyboard accessible? </pre> V Stuart Foote 2013-03-01T16:25:38 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/486 <pre>Is it on anyone's radar to make the LO 4.x template manager keyboard accessible? Tabbing or other keystrokes don't take me from a tab to the list of templates. Even after a mouse click on the My Templates box/group, I have not found any keystrokes that allow me to select any particular template. Mouse required on all fronts? This makes the new TM really cumbersome for a keyboard user. A mobility impairment makes mouse usage troublesome for me. I would also request an option to show the templates as a simple list instead of thumbs. I know some people seem to like the "icon" way of navigating, but I'm not one. -- View this message in context: http://nabble.documentfoundation.org/keyboard-accessibility-of-new-template-manager-tp4040947.html Sent from the Accessibility mailing list archive at Nabble.com. </pre> ktc 2013-03-01T15:38:46 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/476 <pre>Hello list, My name is Jonathan Nadeau and I'm the executive director of the Accessible Computing Foundation located here http://www.accessiblecomputingfoundation.org I'm looking to fund some developers to fix some accessibility bugs with Libreoffice and the Orca screen reader. I was hoping either someone on the list would be interested in fixing some bugs or that the list might know of some people that would like to earn some money to fix some bugs. Please let me know if this is not the right place to look for help or if there are any other suggestions. Thanks for your time and help. </pre> Jonathan Nadeau 2013-02-21T22:33:26 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/475 <pre>I'm referring specifically to bugs 50926 and 56031 concerning interactions between LO writer and at-spi. If this looks like a couple of weeks' work for someone with the right skills I can probably find funding for it ... the only alternative I now see is going back to dual-boot. Oh and from the comments on 56031 there's a box of beer in it as well :-) So, are there mechanisms around to fund people for small tasks like this? I'd welcome any suggestions cheers Peter </pre> Peter Rayner 2013-02-15T07:51:27 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/473 <pre>Hi everyone, Following Tom's suggestion, I am posting here my own LibreOffice accessibility wish list. While these are all important needs, I am trying to rank them in order of priority. While the ranking is mine, the list itself was prepared with the generous assistance of software developers at Lanedo, when I needed detailed objectives for funding proposals I sent last year. Here it is: Heading in writer not exposed properly to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35105 Hyperlink in writer not exposed properly to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35107 A list box in writer not exposed properly to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35110 Combo-box in writer not exposed properly to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35111 A section in writer not visible at all to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35112 Spin-button in Calc not exposed properly to AT-SPI : https://bugs.freedesktop.org/show_bug.cgi?id=35</pre> Fernando Botelho 2013-01-31T20:45:05 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/463 <pre>Hi everyone, I am having difficulty with: libreoffice_1:3.6.2~rc2-0ubuntu4_all.deb The problem is that the Orca screen reader is not able to read cell coordinates in Calc as it used to back in OpenOfice. The Orca and at-spi versions I am using are: gnome-orca_3.7.0.94-0ubuntu0.1_all.deb and at-spi2-core_2.6.1-0ubuntu0.1_i386.deb The files that seem to be involved are: /usr/lib/python3/dist-packages/orca/scripts/apps/soffice/speech_generator.py /usr/lib/python3/dist-packages/orca/scripts/apps/soffice/braille_generator.py Functions that have the bug: def _generateRowHeader(self, obj, **args) def _generateNewRowHeader(self, obj, **args) def _generateColumnHeader(self, obj, **args) def _generateNewColumnHeader(self, obj, **args) Specific line in the code: table in self._script.dynamicRowHeaders In this line table is searched as a dictionary key: self._script.dynamicRowHeaders The expectation is that the keys be constant whereas a variable of the table type is not. So this error is generated: type T</pre> Fernando Botelho 2013-01-23T12:07:09 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/458 <pre>Dear sirs, I expect to use in the future the Libre office 3.5.4.2 Version. I have a bad vision especially in contrasts and colours.Today I tried using libre office writer and calc, but the problem was the icons that I could'nt see well. Some of them have a low density so that I really can't see them. I work with Zoom text 9.1 in inversed video My question is : how is it possible to enlarge the icons and contrast them ? I am a french speaking person and if you please answer me in french it could be kind thanks a lot for your answer best regards Catherine RUSSON Insee - Dr Ile-de-France Assistante Section Formation Service de l'Administration des Ressources ( : 01.30.96.91.94 </pre> Russon Catherine 2013-01-09T15:36:08 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/446 <pre>Hi all, I just downloaded the LibreOffice 4.0 beta 1 and installed it on my windows box. In the installer i saw a checkbox which should enable accessibility so i checked it. but after the installation has completed i started writer and i figured out that it was as non accessible as the 3.6 versions. even 3.5 was more accessible on windows with NVDA and Jaws. are you currently working on that cause i read in the 4.0 changelog that accessibility apis have been removed. or is there something i don't know or i have missed out? running win xp, java 7 update 9 and the integrated java access bridge. tested with daily build of NVDA and Jaws 12. greetings, simon </pre> Simon Eigeldinger 2012-12-10T20:13:44 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/442 <pre>Have posted some Wiki updates to the a11y &amp; Java windows accessibility roles FAQ. The Wiki changes address the accesibility support now restored in the LibreOffice 3.6.4 and 4.0 development builds, and cleanup some of the text related to configuring Java based accesibility on 3.5.7 builds. http://wiki.documentfoundation.org/Faq/General/a11y/Java -- View this message in context: http://nabble.documentfoundation.org/Wiki-updates-a11y-Java-Accessibility-for-Windows-users-Wiki-tp4023225.html Sent from the Accessibility mailing list archive at Nabble.com. </pre> V Stuart Foote 2012-12-08T02:16:11 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/437 <pre>Hi :) Is there any chance of someone putting forwards a couple of funding proposals from the Accessibility List, perhaps as a Team effort?  I think less than 1 line, just a sentence with a hopeful guess at how much cash might be needed.  A few different proposals with very different amounts might help.  If we had success with a smaller budget the larger items might happen later.  I kinda see Stuart as a potential team leader as he seems to have done an excellent job at that in the past (although that was more by accident rather than being deliberate and i'm not sure he was keen on finding himself in that position).   So far there have been 2 suggestions and i think either would cost a lot.  I can't remember the other one but mine was 1.  to employ a part-time or full-time dev team leader or supervisor with part of her/his remit being to inspire people to volunteer and join her/his team for working on code for Accessibility issues.  1.  a)  Part of my suggestion was that another part of t</pre> Tom Davies 2012-12-06T17:27:23 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/433 <pre>Hello. This is regarding Libreoffice 3.6.4 and its support for assistive technology. I'm using a Windows 7 Pro 32-bit machine installing the latest version of Java from the Ninite installer; JAB is enabled via the control panel under Ease of Access. My screen reader is NVDA 2012.3. While installing this latest version I was careful to check the box for enabling support for assistive technology. When I loaded Writer I received no feedback while navigating through menus. I know the keystrokes for enabling a.t. support in the Options dialog and I did this and then restarted Writer: this time I received a little more feedback. This means that it is likely that a.t. support was in fact disabled even though I checked the appropriate box during installation. I have checked with a sighted person who verifies that a.t. support is enabled in the options dialog. While menus spoke and I can receive text feedback while moving through a document dialog boxes are usually silent except for standard dialogs such as the Ope</pre> David Goldfield 2012-12-06T14:43:58 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/427 <pre>Just out of curiosity, who is on this mailing list and is interested in seriously helping out with getting accessibility issues fixed with LibreOffice? When I say "interested in seriously helping out", I mean people who would help doing some * QA (Quality Assurance) work -- this involves helping confirming accessibility bugs, and testing fixes to the bugs. The QA Team will even help mentoring people who are willing to do this! * helping out at conferences -- in your region -- this involves as little as dropping of pamphlets ... to as much involvement as manning a booth and discussing accessibility advantages with LibreOffice * discussing topics here on this list and actively seeking good/solid feature suggestions for our developers ... talk is cheap, but, if talk leads to making the accessibility attributes of LibreOffice more compelling as a tool for people who are in need of an office suite with solid accessibility features, then it is worth it. If you have design ideas about the user inter</pre> Marc Paré 2012-12-03T17:22:47 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.accessibility/416 <pre>Following the recent discussion here, I ran a simple search of Bugzilla: https://bugs.freedesktop.org/buglist.cgi?quicksearch=libreoffice+orca which should pick up most of the ATK-related accessibility bugs. What is interesting to note is that all of the bugs are open, none has been assigned to anybody and there are no patches for any of them (unless I missed one in my review, in which case apologies are due). The bugs appear to have been properly reported and to be specific enough for someone familiar with the code to fix. This is not a complaint or a criticism and shouldn't be construed as such. </pre> Jason White 2012-11-22T04:52:08 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.documentfoundation.libreoffice.accessibility