Accessibility bug triage flow
Bugs
2 locations to look at - Github & ADO
- Github:
Majority of a11y bugs are reported here by internal and external customers.
- ADO:
A process we recently started. Reasons: 1) How internal customers (e.g. partner team in E&D) report bugs directly to us. 2) How Scorecard pull bug metrics from here and calcuate score for E&D products (including FluentUI).
How to triage
Determine severity
- High
- Crash; stop page.
- blocking user to accomplish a certain action for a high-usage scenario (e.g. cannot navigate to an option inside a dropdown, cannot tell an item is disabled in high contrast mode)
- Medium
- Non-blocking MAS/WCAG 2.1 and usability issues in either low/high usage scenarios.
- Low
- Minor issues
- Low usage scenarios that fix involve high risk of regression.
Triage guide
Sometimes it's not clear what the expected behavior should be. In that case you can choose one of the following channel to get help:
- Ask Component Owner
- Ask Ben Truelove (designer)
- Ask in FluentUI Accessibility channel
- For DetailsList related, Ask Chris Schlechty
- Ask Sarah Higley (a11y expert who can help with any a11y related questions, esp. on questions related to Dropdown/Combobox/Callout/speicific screen reader)
For bugs belongs to external teams:
- Narrator: https://microsoft.visualstudio.com/OS/_queries?tempQueryId=13f71e8b-5c18-4e9d-977e-6f8f19fcd557
- NVDA: https://office.visualstudio.com/OC/_queries?tempQueryId=4f07f487-71cb-4323-84a7-64700bce214f
- VoiceOver: TBD
Known challenges
- Lack of design documentation
- We will have good component spec going forward with our converged component, but that will take time.
- Try to write down notes here when you find fit.
- Some of our (more complex) components tend to have more bugs. This is because user would have more complex use cases and the components were not orignally designed with a11y in mind as hard requirement.
- External bugs (e.g. Narrator bugs) need to be reported to external team and we have less control over the fix.
- WCAG 2.1 & Reflow: currently required to be fixed by March 2021
- Track metrics: codesandbox
References
- MAS/Microsoft Accessibility Standard
- WCAG 2.1
- Support matrix
- Basic learning materials
- High Contrast Design Guide (from Ben Truelove)