From 40a355a42d4a9444dc753c04c6608dade2f06a23 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Fri, 19 Apr 2024 03:13:27 +0200 Subject: Adding upstream version 125.0.1. Signed-off-by: Daniel Baumann --- docs/bug-mgmt/processes/accessibility-review.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs/bug-mgmt/processes/accessibility-review.md') diff --git a/docs/bug-mgmt/processes/accessibility-review.md b/docs/bug-mgmt/processes/accessibility-review.md index 3358defd7e..090d83acfe 100644 --- a/docs/bug-mgmt/processes/accessibility-review.md +++ b/docs/bug-mgmt/processes/accessibility-review.md @@ -54,9 +54,12 @@ bug for the accessibility review. Otherwise, particularly for smaller changes, you may do this on an existing bug. Note that if you file a new bug, you will need to submit the bug and then edit it to set the flag. -Once the review is done, the accessibility team will set the a11y-review -flag depending on the outcome: - +During the review process, the accessibility team will modify the a11y-review +flag: +- assigned: The review has been triaged by the team and an engineer has been assigned + to the review. If the flag has been set on a bug filed specifically for the purposes + of review (i.e., the bug does not have additional engineering work attached, and the bug is not a meta bug) the review assignee will assign the bug to themselves. + Otherwise, they'll comment on the bug so you know who they are :) - passed: Either no changes are required, or some changes are required but the accessibility team does not believe it is necessary to review or verify those changes prior to shipping. Generally, a review will not be passed if -- cgit v1.2.3