Date: prev next · Thread: first prev next last


Hi :)
I think you have to edit the wiki to add your own comment in a relevant place.  If you can check 
out other items on the page you find that some have 3 or 4 reasons why their idea should be dealt 
with.  


I was thinking about adding something about organisations needing to be able to show the software 
they use could theoretically be used by people by people that have accessibility issues.  Given 
real discrimination out there they probably wont have to show it really all works but at least it's 
a 1st step to breaking down some of the discriminatory practices by reducing the amount of excuses 
they can invent.  

Regards from
Tom :)  





________________________________
From: Jaap van de Putte <info@2useit.nl>
To: accessibility@global.libreoffice.org 
Sent: Tuesday, 4 September 2012, 7:44
Subject: Re: [libreoffice-accessibility] wiki.documentfoundation.org - Vote_for_Enhancement: 
Implement the IAccessible2 accessibility API

Hi,

I would like to vote and I have looked on the wiki page but I do not 
know how to vote there ....

Jaap van de Putte

Op 3-9-2012 21:48, V Stuart Foote schreef:
Folks,

I've placed Bug 39956 - Implement the IAccessible2 accessibility API onto the Document 
Foundation Vote for Enhancements wiki found here:

https://wiki.documentfoundation.org/Vote_for_Enhancement

Most folks would be surprised to find just how spotty and incomplete Accessibility and Assistive 
Technology tools offered with LibreOffice are. But, I think all can agree that the current UNO - 
Java Accessibility Bridge continues to present Java Runtime Environment configuration issues for 
Windows. While Linux/Unix users supported with ATK and AT-SPI have had it better, there are a 
fair number of unresolved AT issues that affect all LibO/AOo users. Emerging AT-SPI2 efforts of 
the Open Accessibility (A11y) Group that require integration into LibreOffice are backing up.

Implementing IAccessibility2 (NOT a trivial technical issue) would improve accessibility and 
Assistive Technology tools across all implementations of LibreOffice, and during the effort 
would present an opportunity to fully implement A11y recommendations.

Please review the issues affecting this often overlooked aspect of LibreOffice, and let the BOD 
and Developer community know more consistent and complete accessibility support is an effort 
worth pursuing by commenting on the "Vote for Enhancements" wiki.

Regards,

Stuart

refs:

http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2/overview
http://www.openoffice.org/api/docs/common/ref/com/sun/star/accessibility/module-ix.html
http://www.linuxfoundation.org/news-media/announcements/2010/07/linux-foundation-delivers-new-licensing-terms-testing-tools-accessi
http://developer.gnome.org/accessibility-devel-guide/stable/gad-how-it-works.html.en







-- 
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted




-- 
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.