Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


V Stuart Foote píše v Ne 03. 02. 2013 v 22:21 +0000:
I've created a new Bugzilla tracking metabug, fdo#60251, for Accessibility and Assistive 
Technology issues on Window OS. Hope this will help to track all accessibility issues across the 
LibreOffice projects. So, we now have three that are active, one for each major OS branch with 
some cross listing. May have to do something similar for the mobile OS as they evolve.

https://bugs.freedesktop.org/show_bug.cgi?id=36549 for Linux GNOME Orca and AT-SPI2/ATK
https://bugs.freedesktop.org/show_bug.cgi?id=55571 for Apple OSX Apple Accessibility API
https://bugs.freedesktop.org/show_bug.cgi?id=60251 for Windows OS Accessibility and the JAVA 
Access Bridge

Folks should review these and please submit known issues as new bugs or enhancement requests.  
And of course I hope it will help in all aspects of making Accessibility and AT support with 
LibreOffice the preferred choice for all operating systems and platforms.

Also, I apologize to those Devs & QA folks that I buried today with email updates as I sorted 
through the existing bugs and metatagged with an ACCESSIBILITY: value in the title.

Great work!

Could you please mention these meta bugs at
https://wiki.documentfoundation.org/Most_Annoying_Bugs in the section
"Specialized MABs"?

Thanks a lot for sorting this.

Best Regards,
Petr



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.