Bugzilla

### New Flag
- (required) The name of the flag: a11y-review
- (required) Use this to request accessibility review for a UI addition or change.
- (required) Which products/components the flag should appear in: bugzilla.mozilla.org, Core, Conduit, DevTools, Firefox, GeckoView, Pocket, Toolkit, Tree Management, WebExtensions
- (required) Whether the flag applies to bugs or attachments: bugs
- (required) Whether the flag is requestable (i.e. users can ask for flags of this type to be set): yes
- (required) Whether the flag should be requested from a specific person: no
- (required) Whether the flag can be set multiple times: no
- (optional) If flags of this type are requestable, the group allowed to request them, if any: anyone
- (optional) The group allowed to grant/deny flags of this type, if any: the accessibility team: :asa, :eeejay, :jamie, :marcoz, :morgan, :svoisen, :yzen
- (optional) CC list for request notifications, if any (not recommended, use component watching): the accessibility team as above, or accessibility@mozilla.com. I don't think we can use component watching here, since these bugs might be filed in multiple components? Or can we watch a flag?

Additional info:

- Emma noted this would need to be a tracking flag.
- If possible, it should have the values: requested, passed, changes required.
- It should replace the existing a11y-review requestee flag on both bugs and attachments.
- We'd like the flag to trigger a comment template as included below.

#### Template
```
Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

All user interface additions and changes must meet the Mozilla Accessibility Release Requirements:
https://wiki.mozilla.org/Accessibility/Requirements).
Please describe the accessibility requirements you considered and what steps you've taken to address them:
Describe any areas of concern to which you want the accessibility team to give special attention:
```

### New Flag
- (required) The name of the flag: a11y-review
- (required) Use this to request accessibility review for a UI addition or change.
- (required) Which products/components the flag should appear in: bugzilla.mozilla.org, Core, Conduit, DevTools, Firefox, GeckoView, Pocket, Toolkit, Tree Management, WebExtensions
- (required) Whether the flag applies to bugs or attachments: bugs
- (required) Whether the flag is requestable (i.e. users can ask for flags of this type to be set): yes
- (required) Whether the flag should be requested from a specific person: no
- (required) Whether the flag can be set multiple times: no
- (optional) If flags of this type are requestable, the group allowed to request them, if any: anyone
- (optional) The group allowed to grant/deny flags of this type, if any: the accessibility team: :asa, :eeejay, :jamie, :marcoz, :morgan, :svoisen, :yzen
- (optional) CC list for request notifications, if any (not recommended, use component watching): the accessibility team as above, or accessibility@mozilla.com. I don't think we can use component watching here, since these bugs might be filed in multiple components? Or can we watch a flag?

Additional info:

- Emma noted this would need to be a tracking flag.
- If possible, it should have the values: requested, passed, changes required.
- It should replace the existing a11y-review requestee flag on both bugs and attachments.
- We'd like the flag to trigger a comment template as included below.

#### Template
```
Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

All user interface additions and changes must meet the Mozilla Accessibility Release Requirements:
https://wiki.mozilla.org/Accessibility/Requirements
Please describe the accessibility requirements you considered and what steps you've taken to address them:
Describe any areas of concern to which you want the accessibility team to give special attention:
```