Get Involved/accessibility: Difference between revisions

From KDE Community Wiki
(Created page with '__NOTOC__ == Getting Started with KDE Accessibility == Accesibility|left By making KDE available to a wider audience, you will help make computing ea...')
 
No edit summary
(One intermediate revision by one other user not shown)
Line 1: Line 1:
__NOTOC__
== Getting Started with KDE Accessibility ==
== Getting Started with KDE Accessibility ==


Line 21: Line 20:
* Sebastian Sauer (<span class="mailme">mail at dipe dot org</span>)<br />most involved with QAccessible/KAccessible
* Sebastian Sauer (<span class="mailme">mail at dipe dot org</span>)<br />most involved with QAccessible/KAccessible
* Contact Will Entriken (<span class="mailme">kde dot org at phor dot net</span>) if you are interested in mentoring
* Contact Will Entriken (<span class="mailme">kde dot org at phor dot net</span>) if you are interested in mentoring
[[Category:Needs Attention]]
__NOTOC__

Revision as of 13:47, 10 March 2016

Getting Started with KDE Accessibility

Accesibility
Accesibility

By making KDE available to a wider audience, you will help make computing easier for people with visual, auditory and motor disabilities. Some governments and large companies have specific criteria for procuring software. By following standardized procedures for documenting the compatibility of KDE with accessibility technology, KDE software will be a much better candidate for users with special needs.

Communicating with the team

There are many ways to get in touch with the team:
The team discusses activities on the kde-acessibility mailing list, learn about mailing lists.
The team also meets in #kde-accessibility on irc.freenode.net. Learn more about IRC.
Also, see a list of people currently working on the project.

First Steps

The main activities of the project include assessing and documenting the accessibility features of KDE. This is described at The KDE Accessibility HOWTO.

Just open the help section of KDE. There are lots of opportunities to find and replace outdated screenshots or make sure that descriptions in the text are consistent with the interface in the software it is documenting. If you start with this, it should be simple to fix and commit your first contribution.

Mentor program

Getting started in a big project can be hard. Here are some people that are willing to help you on your way:

  • Jeremy Whiting (jpwhiting at kde dot org)
  • Sebastian Sauer (mail at dipe dot org)
    most involved with QAccessible/KAccessible
  • Contact Will Entriken (kde dot org at phor dot net) if you are interested in mentoring