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


Christoph Noack wrote on 2010-11-28 13.08:

Sorry to ask - but who asked? :-) It is a great sign, since this topic
is very important and requires quite some experience. In the past, I
felt very safe with √Čric Savary covering this task for OOo and OOO.

It would be great to know who might take care :-)

someone from the audience at LinuxDay Dornbirn talked to me about our accesibility plans. She was disabled herself, and proposed a separate list with lower mail volume, where developers and people in need of accessibility could exchange themselves.

Of course, this only makes sense when we have someone taking care of this - that's why I share this idea. :-)

Because of the missing working space for accessibility issues, I already
added that topic to the "Design" wiki page draft some days ago [1].
Thus, from my point-of-view, we may add this to the LibreOffice Design
team mailing list as well ... as a starting point.

I guess the main concern is, that especially for people in need of accessibility, following large mail threads not related to that topic, can be a problem - so a dedicated list indeed might make sense.


Florian Effenberger <>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/ @floeff

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.