Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A62F2EE1F for ; Fri, 15 Mar 2013 15:57:16 +0000 (UTC) Received: (qmail 1864 invoked by uid 500); 15 Mar 2013 15:57:16 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 1625 invoked by uid 500); 15 Mar 2013 15:57:16 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 1610 invoked by uid 99); 15 Mar 2013 15:57:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 15:57:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jogischmidt@gmail.com designates 209.85.212.169 as permitted sender) Received: from [209.85.212.169] (HELO mail-wi0-f169.google.com) (209.85.212.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 15:57:11 +0000 Received: by mail-wi0-f169.google.com with SMTP id l13so781761wie.0 for ; Fri, 15 Mar 2013 08:56:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=t99bnElVbBgHgt7nh1DTBrZEmyQkRT9I3X5j7CQMXiU=; b=q7FL1VFXdx7qFZbQvOSUc8Y+Kiv3F3dxHY2C9LZdDbRfLbq6cLCFzOp8rNul/YU7e7 1yROQidoC5AgSgXGoRNuVwMUOg3hcWfa8GLVG/9AUGaUA5heFOFaYMm9XBSUrkHVkofM RXdpoX63Txgf922yTVTXmT8j2iv6gTR1xlog4/29ghSq1Z8gd8UfojchjqChyDRyydvi E3aJIjnmHjygHXFogXRx5KDlMBwbxvoBzNowWKbEKOVkd3EXQo6XvYQe2sZQ1+x+6yXL kLv6y12pF7hgbehv36VUMb49xLkSsAWKXCLyG2N4QR93C6sLZxn83UYVmmtQAIDNVNBH cJUw== X-Received: by 10.180.38.101 with SMTP id f5mr3954356wik.25.1363363009934; Fri, 15 Mar 2013 08:56:49 -0700 (PDT) Received: from [9.155.131.123] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id dm9sm3601544wib.3.2013.03.15.08.56.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Mar 2013 08:56:48 -0700 (PDT) Message-ID: <514344BF.10102@gmail.com> Date: Fri, 15 Mar 2013 16:56:47 +0100 From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: dev@openoffice.apache.org Subject: Re: Problems with Accessibility in Open Office References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 3/15/13 4:38 PM, Waldorf PC wrote: > Hi there: > > So, what you are saying is that I will need to use the JAVA > Accessibility API along with that Open Office application? Honestly, > native controls work much better for assistive technologies. I am not > sure how much your developers are familiar with coding for > accessibility; however, there are some specific things that can be > done if you want your application to use its own UI rather than native > controls. Java Accessibility is what we had today and which has limited functionality. That is the reason why we work on the IAccessibility2 integration. It makes more sense to focus on this and I am sure your knowledge and experience will be of big help for us when we have more to test for you. Juergen > > I tried using function f6 upon opening the application, but i had no > such luck. I still cannot choose the template I want, like the writing > document or spread sheet. > > i thank you so much for your diligence with this matter. You guys are > so great! :) > > On 3/15/13, Joost Andrae wrote: >> Hi Reina, >> >>> >>> My name is Reina Grosvalet, and I am displeased about the fact that >>> Open Office is not accessible for blind computer users, as this >>> program does not work with screen reading and other assistive >>> technologies. Blind people, just like everyone else, want a free word >>> processing option that works just as well as MS Office. Blind >>> freelancers can especially benefit from your program beingaccessible, >>> as well as blind entrepreneurs, students and professionals. >> >> Some of the tools you're using with MS Office don't work well with other >> programs that use it's own UI controls instead of native controls. >> OpenOffice currently exposes it's information to accessive technology >> via Java Accessibility API on Windows and via GNOME Accessibility API on >> Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers >> here are currently working on support for IAccessible2. >> >> https://en.wikipedia.org/wiki/IAccessible2 >> http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support >> >> Have a look here: >> >> http://www.openoffice.org/ui/accessibility/at-support.html >> http://wiki.openoffice.org/wiki/Accessibility >> >>> >>> Because I am a certified 508 Compliance Analyst, I can provide >>> detailed feedback concerninghow you can make your program one hundred >>> percent accessible, so the millions of blind computer users around the >>> world will be able to benefit from it along with everyone else. If you >>> need proof of my certificates, I will be glad to send them to you. A >>> plus is that I am also totally blind, so I can provide feedback from >>> the point of view of someone who is blind. >>> >>> in order to give you an idea of some of the problems I see, I am going >>> to provide you with a mini report below. this report states: >>> >>> 1. The installer has buttons that are clearly labeled with text that >>> can be clearly accessed using keyboard navigation. this is a plus >>> because a blind computer user is able to successfully install the >>> program on his or her computer without any sighted help. >>> 2. The buttons in the installer all have corresponding access keys, >>> like alt+n for next and alt+f for finish. This is very helpful for >>> screen reader users and for those who use assistive technologies >>> because these access keys allow such users to complete functions >>> quickly. >>> 3. Upon opening the program, however, i notice that a blind computer >>> user is not able to access any of its functions using keyboard >>> navigation. the blind user cannot select the type of template heor she >>> wishes to use, like a spreadssheet or text document. Drop down menus >>> cannot be accessed using any form of keyboard navigation, like using >>> the alt key to access the menus like in the windows operating system. >> >> Use funktion key F6 to toggle between the menu, menu bar and tool bars >> >>> >>> as soon as you contact me, I can construct a detailed report that >>> contains each problem I see as well as provide detailed fixes to these >>> problems. It is my hope that Open Office becomes completely >>> accessible, so people with disabilities can utilize this software and >>> enjoy its benefits. >>> >> >> Kind regards, Joost >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org >> For additional commands, e-mail: dev-help@openoffice.apache.org >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org