---
robots: nofollow, noindex
tags: a11y
---

# FY21 Accessibility Planning

Notes:
- Update on FY20 progress
- Update on FY21 Fabric controls

Next Steps
- Collect data to understand the remaining impact
- Come up with plan on for the current set issues
- Set up the goals for project
- Decide on the remaining components
- Decide on items

# FY21 Accessibility Plan

# Short Term

## Next Steps
- Audit all our a11y issues (across GitHub and ADO)
- Come up with a prioritized list of issues
- What's the actual principles (how do we prioritize? By impact? By impact and product affected?)
- Create a cut line
- Make sure the code owners file is up to date according to Component for a11y
- Determine what fits in July Project?

- Where is our component design source of truth?
- Is is really Ben True?
- Is there a document somewhere?
- Is a mix of Ben and Component authors?
- Is it just the ARIA spec?
[Xu]: we first look at ARIA spec. And for more complex scenarios we ask Ben truelove and component owners for expected behaviors.

- We need help from an a11y experts are these folks we can rely on:
- Jarij (sp)
- Sarah?
- Chris Sheverly? DetailsList on point person
- Ben True (from Design?)

- Scorecard
- Need to document how the scorecard system work (main audience for this are developers)

# Long Term

## Why?
*what are our goals? what are we trying to accomplish*

1 Markus - the best UI library that implements a11y
- All 70+ components adhere to the ARIA spec
- All 70+ components support new WCAG 2.1 guidelines
- All 70+ components adhere to the MAS guidelines
- Accrediation by some a11y standards body
2 Legal and Business impacts that a11y have on our Microsoft Products

- All 70+ components support new WCAG 2.1 guidelines
- All 70+ components adhere to the MAS guidelines

## What?
- Clear documentation setting the aligned/agreed expectations with Eng/PM/Anita

## How?
- How to prioritize
- How to resource dev to fix bugs
- How do customers reach us for urgent issues
- Improve on areas (e.g. get notified with stale bugs; design spec for a11y) we are lacking

## GitHub
- Highly recommend the use of our Bug Template - create systems that leverage this template to help us and other teams

## ADO
- Highly recommend the use of our Bug Template - create systems that leverage this template to help us and other teams
- Make sure we can plug the template into various bug filing systems and people that file issues