Accessibility/GettingInvolved

GettingInvolved

Revision 9 as of 2010-11-06 16:14:21

	Accessibility Team
	Home Getting Involved User Documentation Contacts

	Development
	Specifications Software Goals Bugs and Testing

	Outreach
	About the Team Meetings Personas Team Reports

Accessibility Team

Consider joining the Accessibility Team to keep up to date on current issues with accessibility. However, joining is entirely optional. There are many ways to help with accessibility in Ubuntu.

An active team presence which includes community members from the Accessibility Team and Canonical is available
- Come on in and talk to us using your favorite chat client - irc.freenode.net #ubuntu-accessibility
- You can contact us using your web browser if you prefer
Items which require in-depth discussion or do not need an immediate response can be done using the mailing list.
Developers are invited to join us in our discussions using the above. Development specific discussions should take place on the developers mailing list.
Some users requesting assistance with accessibility prefer the forums.
You may also connect with us directly using the Contacts page.

We welcome you to join in and make Ubuntu available for all users.

Testing

We also offer a testing crew to assist developers concerned with ensuring that their application is accessible. Please see specialization within the Accessibility team for details, but basically, you need to:

Sign the Code of Conduct
Although not really required, read the How to Triage guide. It does help to read it
Request a mentor by following the instructions on Accessibility/Testers where you will need to provide:
- An area of specialization (if you have any)
- Timezone
- Time when available

Members of the Accessibility Team and Canonical employees are available in #ubuntu-accessibility to answer any questions you might have.

ToDo

If you would like to get involved with the Accessibility Team, please take a look at our ToDo page. This is a place to track those items that need a little love.

Bug Tag Assignment

There is a need for quick triage to be performed on Bugs that are tagged as accessibility bugs. During the triage process, all bugs affecting accessibility need to be tagged. The tag used is a11y.

Bug Importance

All bugs affecting accessibility should have an importance set when the bug status is changed to confirmed or triaged. More complete documentation is available on the Bug Importance Page, but the two classifications are: