---
# System prepended metadata

title: Potential issues for Tristan (LEAP) to work on

---

---
robots: nofollow, noindex
---
# Potential issues for Tristan (LEAP) to work on

- [x] https://github.com/microsoft/fluentui/issues/16263
- [x] https://github.com/microsoft/fluentui/issues/16228
~~- https://github.com/microsoft/fluentui/issues/16184~~
- [x] https://github.com/microsoft/fluentui/issues/14191
- [x] https://github.com/microsoft/fluentui/issues/14170
- [x] https://github.com/microsoft/fluentui/issues/13323 (A little more advanced)
- [x] https://github.com/microsoft/fluentui/issues/16878
- [x] https://github.com/microsoft/fluentui/issues/13974
- [x] https://github.com/microsoft/fluentui/issues/13879
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/7222
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/6397 and https://github.com/microsoft/fluentui/issues/14891 (more advanced, DetailsList -- let me know if you want this one)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10251 (WHCM)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10297 (WHCM)
- [x] https://github.com/microsoft/fluentui/issues/16059 (this one has a bigger overhaul of the Rating widget for the future, but also a few quick fix possibilities now. I think it'd be a good one to use to explore how the current roles and attributes affect screen reader accessibility, and also what possible short-term fixes might be good. Let's chat about this one before you start implementing fixes)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10292 (The keyboard interaction for the close button is already handled IIRC, so it should just be a visual change to make it show up on focus)
- [x] https://github.com/microsoft/fluentui/issues/10911 (Style fixes to hide social footer + modal so we can remove MWF)
- [x] https://github.com/microsoft/fluentui/issues/17283 (ContextualMenu focus issue)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10688 (Something's up with the id references in the virtualized combobox. Take a look, and let me know if you have any questions, or run into any blocks)
- [x] https://github.com/microsoft/fluentui/issues/17182 (Facepile)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10795 (HCM focus style)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10549 (More styling! Not HCM this time for a change, though)
- [ ] https://github.com/microsoft/fluentui/issues/17502 (Virtualized GroupedList/Grouped DetailsList row index calculation)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10892 + https://github.com/microsoft/fluentui/issues/17628 (Contextual menu, updated with more specific github issue)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11037 (Splitbutton exploration! One straightforward fix, and one that needs some creativity)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11491 (Should be a quick docs site win. If you want to knock something out quickly, pick this one :D. Also, I didn't add any comments, so take a look at w3c.github.io/aria-practices or w3c.github.io/aria for reference, and feel free to ask!)
- [x] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11604 (It'd be good to first drop a line to the owner of Dropdown, Jon, just to double check the change b/c it'll update the behavior. This also probably wouldn't get ported to v7, but I'm not sure)
- [ ] https://github.com/microsoft/fluentui/issues/17718 (I haven't looked at DocumentCard much at all, just ran across this when working on pickers. I'm guessing there might be difficulty in handling props between the DocumentCard component and its child components.)
- [ ] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11056 (This is another docsite one, and I think it'd be a good one to take on and pay attention to how easy or difficult it is for authors to customize a Fluent control like the CommandBar based on edge-case usage like the one we have in that example. I'll be interested in what you think after you're done!)
- [ ] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/10879 (Modal issue! Explore the tradeoffs to handling it internally vs. providing a good example + docs for consumers to handle it)
- [ ] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11979 (This is a difficult one in terms of a11y -- I'd suggest checking out the native select element behavior on iOS for comparison, and then we can chat about options)
- [ ] https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/11964 (This should be interesting! It's more a general issue than an a11y one, but error handling has a11y-specific considerations, and is an interesting UI challenge)
