Add Accessibility team in the Working Group structure. (#34)

* Add Accessibility team in the Working Group structure.
* Add note about superseding DEP 11.
* Update definition as per accessibility team review
* Clarified budget
* Specified specific roles on the team
* Added mention of annual report in the reporting
* Minor language adjustments
* Added new members
* Changed some logistics
* Simplified language
* Move accessibility team to active folder.

---------

Co-authored-by: Thibaud Colas <[email protected]>
Co-authored-by: Tom Carrick <[email protected]>

Author: 3 people

active/accessibility.md

@@ -0,0 +1,115 @@
+# Accessibility Team
+
+This charter supersedes [DEP 11: Accessibility Team](https://github.com/django/deps/blob/main/final/0011-accessibility-team.rst).
+The Accessibility Team encourages projects maintained by the Django Software
+Foundation to be accessible to as many people as possible.
+We focus on those with disabilities who find it more challenging to use the web.
+
+
+## Scope of responsibilities
+
+The scope of the Accessibility Team includes all projects maintained by
+the Django Software Foundation.
+
+This includes but is not limited to:
+
+- User-facing parts of Django, such as:
+  -  default HTML output in forms
+  -  the Django admin and its default theme, HTML, and UI components.
+- All websites and other software projects maintained by the DSF, such as:
+  -  the Django website
+  -  the documentation
+  -  Django Snippets
+  -  the issue tracker
+
+The scope also includes Django events and other community projects where accessibility
+is a relevant concern.
+
+The responsibilities of the Accessibility Team are expected to change over time,
+and are to be decided by consensus of the team, with input from the Steering Council
+as required. These include:
+
+- Deciding on any accessibility guidelines to follow, such as WCAG.
+- Implementing automated testing to find issues.
+- Coordinating accessibility audits.
+- Coordinating the fixing of accessibility issues and accessibility improvements.
+- Writing and maintaining documentation relating to accessibility. For example:
+  - a statement of commitment to accessibility issues
+  - contribution guidelines
+- Reviewing code that affects the accessibility of any in-scope projects.
+
+Many of these duties can be undertaken by any contributor. The Accessibility Team
+coordinates this work.
+It can step in where contributors are not available and support those who lack the
+knowledge to do so themselves.
+Accessibility Team members are added to a team in the GitHub organization with
+read access to relevant repositories. With this they can be requested to review pull
+requests.
+
+
+## Current members
+
+- Chair: Tom Carrick
+- Co-Chair: Eli Rosselli
+- Steering Council Liaison: Tim Schilling
+- Other members:
+  - Marijke Luttekes
+  - Rahmat Akintola
+  - Sage Abdullah
+  - Saptak Sengupta
+  - Sarah Abderemane
+  - Thibaud Colas
+  - Tushar Gupta
+
+
+## Future membership
+
+The team does not have a fixed size.
+The team decides when new members are needed.
+New members are chosen from a list of volunteers.
+If there are no qualified volunteers the team will place an advertisementon the Django website.
+
+Priority will be given to volunteers who:
+
+- Have disabilities that make using the web or web development more difficult.
+- Have expertise in accessibility.
+- Have a record of contributing to Django.
+
+Members must opt-in to remain on the team on an annual basis.
+They may also leave for any reason.
+
+Members can also be removed by:
+
+- Becoming disqualified by the Code of Conduct working group
+- A vote of the Steering Council
+- The full consensus of the rest of the Accessibility Team
+
+
+## Budget
+
+No budget is required at this time. This will be reviewed at least annually.
+Any changes to the budget may be requested from the board.
+
+
+## Communication channels
+
+The Accessibility team operates in several areas:
+- [Accessibility Forum category](https://forum.djangoproject.com/c/internals/accessibility/26)
+- Public #accessbility channel on [Django Discord server](https://chat.djangoproject.com)
+- Private channel on [Django Discord server](https://chat.djangoproject.com)
+- A private Google Drive folder and Group in the DSF Google workspace
+
+The Accessibility team can be tagged specifically in the following areas:
+
+- The [@accessibility](https://forum.djangoproject.com/groups/accessibility) Forum group tag
+- The [@django/accessibility](https://github.com/orgs/django/teams/accessibility) team in the Django organization
+
+The team meets online once per month.
+
+
+## Reporting
+
+The team posts [public meeting notes](https://forum.djangoproject.com/t/accessibility-team-meeting-notes/26133)
+to the forum. These serve as reports to the DSF Board and Steering Council.
+
+The team produces an annual report that is shared with the Django community.