GettingInvolved
|
Size: 981
Comment:
|
Size: 981
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| 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 Specialisation within the Accessibility team for details, but basically, you need to: | 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: |
| Line 12: | Line 12: |
| o An area of specialisation (if you have any) | o An area of specialization (if you have any) |
|
|
|
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:
- o An area of specialization (if you have any) o Timezone o Time when available
Members of the Accessibility Team and Canonical employees are available in #ubuntu-accessibility to answer any questions you might have.
Accessibility/GettingInvolved (last edited 2010-11-22 22:16:43 by ip98-182-50-39)
