GettingInvolved
|
|
|
Accessibility Team
Consider joining the Accessibility Team to keep up to date on current issues with accessibility. However, joining is entirely optional. 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.
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:
- Medium = A bug which impacts accessibility of a non-core application.
- High = A bug which impacts accessibility of a core application.