From 5fdc9111353681befc435dd8c222bda49d05927d Mon Sep 17 00:00:00 2001
From: chunhtai <47866232+chunhtai@users.noreply.github.com>
Date: Fri, 16 Aug 2024 10:19:06 -0700
Subject: [PATCH] adds team-accessibility to triage workflow (#153575)

add team-accessibility to triage workflow
---
 docs/triage/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/triage/README.md b/docs/triage/README.md
index 69681f26f0..e1f0ee7b7e 100644
--- a/docs/triage/README.md
+++ b/docs/triage/README.md
@@ -72,6 +72,8 @@ In general the flow chart for team assignment is as follows, stopping as soon as
 - If it's about the release process or tooling (e.g., `conductor`), add `team-release`.
 - If it's about the Flutter team's CI or infrastructure, add `team-infra`.
 - If it's about Impeller, add `team-engine`.
+- If it's about accessibility (e.g. `Semantics`, `talkBack`, `voiceOver`), add `team-accessibility`.
+  - If it's specific to a single platform, also add that platform's fyi label.
 - If it's about Cupertino or Material Design, add `team-design`.
 - If it's about text fields or other user-facing text input issues, add `team-text-input`.
   - If it's specific to a single platform, also add that platform's fyi label.