Working on a11y-docs for GNOME Women

[Aline Bessa <alibezz gmail com>]

Hi everybody,

My name is Aline and I've been using GNOME since 2006 almost exclusively. This year, I decided to submit an application for working on the Documentation Project through GNOME Women. Considering some of the tasks, I decided to write a project for helping in a11y developers guide documentation. 

I'm quite sure that this is a big task: I'd like to help reviewing, revising and leaving this guide as a book for GNOME 3.0. I'll need to learn the style of the guide, details about who it helps, the entire accessibility stack, how everything fits together and which points do need to get an improvement (so I can priorize them).

The accessibility task grabbed my attention because I do believe that this issue should get more popular in applications. We're always talking about digital inclusion but we all know that this is not just a matter of money. Many people just can't use a computer properly if it's not adapted to their disabilities and I have no doubts that this isn't a less important topic.

And that's it: I really want to help and I'm sure I'll need your help for planning and coordinating the documentation. In particular, it would be useful to get in touch regularly with people that have been writing the guide.  :-)

Once I like programming, I also dedicated part of my project for writing a demo using GTK+ and ATK (and translating it for Python and C++ as well). I was thinking of doing a simple calendar/clock widget that can be customized for people that have typing disabilities or need special color/contrast settings in the application. Once it's a demo, the app itself can't be very complicated. Instead of focusing on the calendar/clock themselves, I want to emphasize on how easy it is to include accessibility in your app. If you have any ideas, advices or suggestions, please let me know.

I was thinking that helping with the developers guide (including the things I need to learn, planning, coordinating, reviewing, revising, discussing and adjusting) would take me a month and a half. Developing, documenting and translating the demo for Python and C++ would take me two weeks more. I intend to spend the last month focused on other demos, but my priority are the accessibility tasks. Do you think that I calculated time properly? Is it too much for each task? Too little? Please, let me know. :-D

And that's it. Thanks in advance!!!

--
Aline Bessa
GNU/Linux Registered User #452373