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

Hey all.

A question I've been wondering, and that Orca users are wondering, and
that the GNOME accessibility team is wondering is: What's the story with
LibreOffice accessibility? In particular:

* Is the fork so complete that fixes made in OOo will not even be seen
  -- or incorporated into LibreOffice even if they are seen? Or

* Are things from OOo still being cherry picked for inclusion in 
  LibreOffice -- or would be if they were pointed out via bugzilla?


* Is there an active a11y team and/or developers focused on a11y issues 
  in LibreOffice?

And, yeah, I know: It's open source. And getting and building the code
is a zillion times easier than is the case with OOo (for which I'm truly
grateful). So I should just submit patches. :-) Let's pretend we've
already had that discussion with the conclusion being that I sincerely
promise to contribute as soon as I get caught up on my DayJob, Orca
work, GNOME 3 issues, etc., etc. In meantime.... What's the story w.r.t.
the questions above?

Oh, and yes, I already inquired on the accessibility list a couple of
months ago. No one there seems to know and the only advice I got was to
file bugs in both issue trackers. Thus if any of y'all can shed light on
the situation it would be super.

Thanks in advance!
  Orca project lead
  GNOME accessibility team

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


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.