GettingInvolved

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2010-11-01 01:34:17 →
Size: 1618
Editor: 71-209-63-103
Comment: 2010-10-31; CharlieKravetz; tag assignment corrections
← Revision 7 as of 2010-11-02 19:27:19 → ⇥
Size: 2408
Editor: 71-209-63-103
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 specialization within the Accessibility team for details, but basically, you need to: Consider joining the [[https://launchpad.net/~accessibility | 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 [[http://webchat.freenode.net/?channels=ubuntu-accessibility | web browser]] if you prefer

 * Items which require in-depth discussion or do not need an immediate response can be done using the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility | mailing list]].

 * Some users requesting assistance with accessibility prefer the [[http://ubuntuforums.org/forumdisplay.php?f=145 | forums]].

== 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:

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.

  • Some users requesting assistance with accessibility prefer the forums.

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 Wink ;-)

  • 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.

Accessibility/GettingInvolved (last edited 2010-11-22 22:16:43 by ip98-182-50-39)