Get Involved/accessibility: Difference between revisions
Thiagosueto (talk | contribs) m (Minor corrections) |
(- Add Matrix channel) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[File:Mascot konqi-app-system.png|right|x200px]] | |||
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 == | == Communicating with the team == | ||
There are many ways to get in touch with the team:<br /> The team discusses activities on the [https://mail.kde.org/mailman/listinfo/kde-accessibility kde-acessibility mailing list]. [ | There are many ways to get in touch with the team:<br /> The team discusses activities on the [https://mail.kde.org/mailman/listinfo/kde-accessibility kde-acessibility mailing list]. You can learn more about mailing lists [https://kde.org/support/#mailinglists here].<br /> The team also meets at [https://webchat.kde.org/#/room/#kde-accessibility:kde.org #kde-accessibility] on [https://community.kde.org/Matrix Matrix] and [irc://irc.kde.org/kde-accessibility IRC]. | ||
== First Steps & Current Projects == | == First Steps & Current Projects == | ||
The main activities of the project include assessing and improving the accessibility features of KDE. This is described at the [ | The main activities of the project include assessing and improving the accessibility features of KDE. This is described at the [https://techbase.kde.org/Development/Tutorials/Accessibility KDE Accessibility HOWTO]. | ||
Our work is tracked on Phabricator. See [https://phabricator.kde.org/project/view/249/ the Accessibility project] and feel free to become a watcher or a member! There's always plenty to do. Another avenue is to just open the help section for any piece of KDE software. There are lots of opportunities to find and replace outdated screenshots or make sure that descriptions in the text are consistent with the interface of the software it is documenting. If you start with this, it should be simple to fix and commit your first contribution! | |||
You are also free to simply provide insight or report any accessibility issues you might encounter with KDE software to the team. Any help is appreciated! | |||
== | == Mentorship program == | ||
Getting started in a big project can be hard. Here are some people that are willing to help you on your way: | Getting started in a big project can be hard. Here are some people that are willing to help you on your way: | ||
Latest revision as of 07:44, 18 July 2023
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. You can learn more about mailing lists here.
The team also meets at #kde-accessibility on Matrix and IRC.
First Steps & Current Projects
The main activities of the project include assessing and improving the accessibility features of KDE. This is described at the KDE Accessibility HOWTO.
Our work is tracked on Phabricator. See the Accessibility project and feel free to become a watcher or a member! There's always plenty to do. Another avenue is to just open the help section for any piece of KDE software. There are lots of opportunities to find and replace outdated screenshots or make sure that descriptions in the text are consistent with the interface of the software it is documenting. If you start with this, it should be simple to fix and commit your first contribution!
You are also free to simply provide insight or report any accessibility issues you might encounter with KDE software to the team. Any help is appreciated!
Mentorship 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