--- tags: process --- # Accessibility Triage Workflow ## GitHub/ADO Issue workflow The following outlines the process when we receive a11y issues on our GitHub repo. ```flow st=>start: Bug Filed on GitHub e=>end: End op=>operation: Shield Team triages issue shieldPri=>operation: Standard Shield Priortization gitA11yIssue=>condition: A11y Issue? gitA11yNeedsImpact=>condition: Needs Impact Assessed? a11yImpact=>operation: Send to Trusted Testers to determine impact a11yWithImpact=>condition: A11y Issue with Impact masBugAdo=>operation: MAS Issue filed in ADO (60 day timer starts) st->op->gitA11yIssue gitA11yIssue(yes)->gitA11yNeedsImpact gitA11yIssue(no)->shieldPri gitA11yNeedsImpact(yes)->a11yImpact gitA11yNeedsImpact(no)->shieldPri a11yImpact->a11yWithImpact a11yWithImpact(yes)->masBugAdo a11yWithImpact(no)->shieldPri ``` Once an Issue has been assessed by the Trusted Testing team and has a11y impact associated with it, and issue will be filed in ADO ```flow st=>start: Bug Filed in ADO end=>end: Fix & Close Issue shieldADOTriage=>operation: Shield ADO Triage ADOpri=>condition: High Impact? fixOrNoFix=>condition: Fix or No Fix? assignForFix=>operation: Create GitHub issue and assign controlInSLA=>operation: Determine if issue meets the SLA wontFixGitHub=>operation: Close Issue in GitHub & ADO olderThan30=>condition: Older than 30 days? makePri1=>operation: Make Pri 1 st->shieldADOTriage->ADOpri ADOpri(yes)->assignForFix ADOpri(no)->controlInSLA->fixOrNoFix fixOrNoFix(yes)->assignForFix fixOrNoFix(no)->wontFixGitHub assignForFix->olderThan30 olderThan30(yes)->makePri1->end ```