Closed
Bug 1021768
Opened 10 years ago
Closed 10 years ago
Create a11y-review per attachment flag
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: yzen, Assigned: dkl)
Details
(Keywords: access)
Please create a new flag 'a11y-review' with ?, +, and - states. This is for tracking accessibility review of new user facing features as well as any accessibility regressions. Name: a11y-review Description: This flag used to ask the accessibility team to look over a bug. Typically used if a bug has the potential to affect accessibility, regresses accessibility, and/or is a new user facing feature. Products: Firefox OS Whether the flag applies to bugs or attachments: attachments Whether the flag is requestable (i.e. users can ask for flags of this type to be set): Not sure what this means Whether the flag should be requested from a specific person: Anyone Whether the flag can be set multiple times: yes If flags of this type are requestable, the group allowed to request them, if any :n/a The group allowed to grant/deny flags of this type, if any: anyone CC list for request notifications, if any (all valid Bugzilla accounts): marco.zehe@googlemail.com surkov.alexander@gmail.com dbolter@mozilla.com trev.saunders@gmail.com eitan@monotonous.org yzenevich@mozilla.com The tooltip would be something like "used to ask the accessibility team to look over a bug".
Comment 1•10 years ago
|
||
I'd tweak the description to: "This flag used to ask the accessibility team to look over a patch. Typically used if a patch has the potential to affect accessibility, regresses accessibility, and/or implements a new user facing feature."
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to David Bolter [:davidb] from comment #1) > I'd tweak the description to: "This flag used to ask the accessibility team > to look over a patch. Typically used if a patch has the potential to affect > accessibility, regresses accessibility, and/or implements a new user facing > feature." Thanks. So the updated description would be: This flag used to ask the accessibility team to look over a patch. Typically used if a patch has the potential to affect accessibility, regresses accessibility, and/or implements a new user facing feature.
Comment 3•10 years ago
|
||
I would also like to see this applied to other products with user-facing features like Firefox, Firefox for Android, WebDev etc.
Reporter | ||
Comment 4•10 years ago
|
||
Description grammar: This flag is used to ask the accessibility team to look over a patch. Typically, it is used if a patch has the potential to affect accessibility, regresses accessibility, and/or implements a new user facing feature.
Comment 5•10 years ago
|
||
r+ Instead of a set CC list, can't we each just configure our bugmail to listen for these? I think Trevor will shoot himself if he gets nagged too much by front end devs.
Assignee | ||
Updated•10 years ago
|
Assignee: administration → nobody
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Marco Zehe (:MarcoZ) from comment #3) > I would also like to see this applied to other products with user-facing > features like Firefox, Firefox for Android, WebDev etc. The 'a11y-review' flag for bugs is currently set to the following products: Core Firefox OS Firefox for Android Firefox Toolkit Do you want me to do the same products for the new attachment flag as well? (In reply to Eitan Isaacson [:eeejay] from comment #5) > Instead of a set CC list, can't we each just configure our bugmail to listen > for these? I think Trevor will shoot himself if he gets nagged too much by > front end devs. So omit the cc list specified in comment 0 then? dkl
Flags: needinfo?(yzenevich)
Reporter | ||
Comment 7•10 years ago
|
||
Sounds good, David: The same components as for the per-bug flag and omit the cc list.
Flags: needinfo?(yzenevich)
Assignee | ||
Comment 8•10 years ago
|
||
Done
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•