# V7 Accessibility Fixes (July)

### Problems
1. We have some a11y bugs in [Github](https://codesandbox.io/s/github-a11y-dashboard-xuie1) and [ADO](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/ab37cec7-fd8f-4828-99ac-d56e65396ada/) that have been not getting enough attention. Some needs triaging help from our team member/design; some simply requires engineer resource to fix.

2. We are now part of the [E&D A11Y scorecard](http://aka.ms/a11scorecard) and the grading the based on the bugs filed inside ADO. Therefore we need to plan a regular cadence to fix the bugs.

### Appetite
It's not realistic to shoot for fixing all the bugs in July. We should fix bugs based on severity and urgency. Along the way we work on improving documentation and triaging process.

### Solution
Have dedicated dev(s) to fix a11y bugs in July:
- Tomi
- Sarah Higley (maybe)

#### Helpful Links
[E+D A11y Scorecard](https://msit.powerbi.com/groups/me/reports/33bd51b2-8a7a-482e-9f4b-3db81d2d7b04/ReportSectionb37656de02bc118dc42b?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47)
[Fabric Component Import Counts](https://msit.powerbi.com/groups/me/reports/0747523d-9ce3-4676-8525-d9673e54cab6/ReportSection2bbdb4c843a4da9ce76e?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47)

[ADO A11y Bug Template](http://aka.ms/fluentuia11ybug)
[GitHub A11y Bug Template](https://github.com/microsoft/fluentui/issues/new?template=accessibility_issue.md)

#### Priorities of bug fixings:
1. [Active bugs in ADO filed by partner teams](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/ab37cec7-fd8f-4828-99ac-d56e65396ada/).
- If bugs are assessed - address in A11yImpact order (High, Medium, Low)
3. [User-reported High Contrast bugs in Edge Chromium. (This is specific a11y push for this month)](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+is%3Aissue+label%3A%22High+Contrast%22)
- Based on Prioirty and Component usage (no MAS impact assesment on these issues)
- Note this is a point in time problem as the real solution needs to be provide by the Edge Browser
5. Active Bugs filed by our Trusted Test team that impact E+D Scorecard
3.1 [Address untagged issues](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/72920ce5-459e-41af-b901-efa238c3fc81/) (These will turn into either: Component, Sample, Website)
3.2 [Component Issues in the Scorecard](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query-edit/fef39447-5962-4250-bd69-36ec0b9569f9/) (High Impact and > 60 Days)
3.3 [Sample Issues](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/755fd112-3e3a-437d-a0c1-f0615c8a0a5d/) (High Impact, [Component Usage](https://msit.powerbi.com/groups/me/reports/0747523d-9ce3-4676-8525-d9673e54cab6/ReportSection2bbdb4c843a4da9ce76e?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47), and time to replace)
3.4 [Website Issues](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/2abbc7cd-6363-46f7-8138-9afc301b79a9/)(High Impact, Ensure we are A11y Insights clean)
7. [A11y Issues Filed on GitHub](https://pr4hi.csb.app/) (Impact, Component Usage)
- Note: By looking at some of the issues filed they appear as though other trusted testing teams are running passes and they file issues here

Notable Component information:
- DetailsList and variants - Agreement was that only High Impact issues would be taken for fixes by the ODSP team. Over all we are devesting in this component
- Charting is owned by the M365 Admin team
- Date Time package and respective components are owned by the Outlook team - [lorejoh12](https://github.com/lorejoh12)

Conversations we need to have on the side as we make the fixes:
- A11y plan for FY21 - finalize definiations related to scorecard grading.
- [How to triage doc](https://hackmd.io/@fluentui/HJ2XnltCU)
- Getting triage help from experts (Ben, Juraj, Chris)

Goals for this cycle:
1. Fixing bugs based on priority.
2. Complete *how to triage* doc and confirm expectations with experts.
3. Ensure the website is A11y Insights Clean - is this Alices team?

### Risks (Rabbit holes)
There are some known challenges on fixing the bugs:
1. Some bugs require discussion/input/help from component code owner, designer, or a11y experts.
2. Some componets tend to be more problemtic / hard to fix than others due to its complexity or lack of design documentation (e.g. DetailsList, Pickers, Dropdown/ComboBox)

### Reference