tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit 77e85858b76cd864fe7bc75f81745b49081539d5
parent d9a75f13cd9862f3a9361128db9b2a4df94cb788
Author: Morgan Rae Reschenberg <mreschenberg@berkeley.edu>
Date:   Thu, 13 Nov 2025 22:55:16 +0000

Bug 1999799: Update a11y review request docs with deadline changes r=eeejay

Differential Revision: https://phabricator.services.mozilla.com/D272528

Diffstat:
Mdocs/bug-mgmt/processes/accessibility-review.md | 11+++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/docs/bug-mgmt/processes/accessibility-review.md b/docs/bug-mgmt/processes/accessibility-review.md @@ -1,4 +1,7 @@ # Accessibility Review +:::{important} +Review requests must be submitted by *December 1, 2025* for consideration before the end-of-year holidays. Reviews submitted after this date may not receive feedback until January 2026. +::: ## Introduction At Mozilla, accessibility is a fundamental part of our mission to ensure the @@ -28,8 +31,12 @@ what is needed to make user interfaces accessible. To make accessibility review faster, you may wish to try to verify and implement these guidelines prior to requesting accessibility review. -For design reviews, please allow at least a week between review request and expected-engineering-handoff. The deadline for engineering review requests is Friday of the first week of nightly builds for the release in which the feature/change is expected to ship. -This is the same date as the PI Request deadline. +:::{attention} +For *design reviews*, please allow at least a week between review request and expected-engineering-handoff. + +The deadline for *engineering review* requests is the Friday before the first week of nightly builds for the release in which the feature/change is expected to ship. +This is the same date as the Manual QA Request deadline. +::: ## Requesting Design Review Design review should be requested using the Accessibility Review Request