Re: [libreoffice-accessibility] introduction

Hi :)
If you are not sure if someone is subscribed to a list you can always include them in the CC or To 
fields to make sure they do get the message so i have put Jonathan in the To field so he gets to 
see the thread so far.  


I also found this quote from the Users List
"
From: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
To: <users@global.libreoffice.org>

Hi,

Do you have a favorite bug you want to get solved, but cannot do it
yourself? You would even pay some money, but cannot contract a Company
for this?

Here's a simple way how to do this, thanks to www.freedomsponsors.org
<http://www.freedomsponsors.org>

1. Login on www.freedomsponsors.org <http://www.freedomsponsors.org>
2. Copy the URL from Bugzilla and Sponsor it in FreedomSponsors!
3. Enter the amount you are willing to pay and publish the Issue
4. You'll get notified when someone solves the bug so you can pay him

Your advantage is, that you have to pay only when the Issue has been
resolved, so there is no risk with that. Payments are done via Paypal.
Others can join and add their offer to the bug.

Here
<http://www.freedomsponsors.org/core/issue/?s=&project_id=149&project_name=LibreOffice> 
are some existing LibreOffice Issues, if you want to support them.

All the best,
Samuel
"

(thanks to Hylton)

I'm not sure if it helps but it might be a good route.  


Is it time-effective to fix bugs with the current java-based system when the rest of the project is 
moving away from Java on the grounds that Java keeps breaking down or having serious problems?  Is 
it possible to use funding to kick-start a re-write in Python or C++ or something?   Is there 
funding?  

Regards from
Tom :)  





> ________________________________
> From: Caolán McNamara <caolanm@redhat.com>
> To: Sophie Gautier <gautier.sophie@gmail.com> 
> Cc: accessibility@global.libreoffice.org; libreoffice <LibreOffice@lists.freedesktop.org> 
> Sent: Friday, 22 February 2013, 11:27
> Subject: Re: [libreoffice-accessibility] introduction
>
> On Fri, 2013-02-22 at 09:29 +0100, Sophie Gautier wrote:
> > Hi Jonathan,
> >
> > Thanks a lot for your proposal. I'm sending your mail to the developers
> > list so we are sure they are aware of it.
> >
> > Kind regards
> > Sophie
> > On 21/02/2013 23:33, Jonathan Nadeau wrote:
> > > Hello list,
> > >
> > > My name is Jonathan Nadeau and I'm the executive director of the
> > > Accessible Computing Foundation located here
> > >
> > > http://www.accessiblecomputingfoundation.org
> > >
> > > I'm looking to fund some developers to fix some accessibility bugs with
> > > Libreoffice and the Orca screen reader.
>
> Nadeau isn't cc'ed on Sophie's original email and I don't know if he's
> subscribed to any of these email lists, but I think it's worth
> mentioning that the work in progress of moving our dialogs to the gtk
> builder file format now makes it super super easy to: 
> a) set that a label is the right mnemonic widget for something else,
> which sets up the default a11y label for, label by relationships between
> them
> b) add a11y descriptions, a11y names, explicit label-for, label-by and
> member-of etc relations
>
> I'm not particularly a11y experienced, but I fired up orca a few weeks
> ago and tweaked our a11y support a bit until it read out the
> "format->title page" dialog the same way as it would read it if it was a
> native gtk dialog.
>
> Obviously there's a lot more a11y-wise to just our dialogs, but at least
> for those new-format dialogs anyone with experience in tweaking gtk a11y
> issues via glade can directly apply that experience to our new dialogs.
>
> C.