Template responses for Shield

--- robots: nofollow, noindex tags: shield --- # Template responses for Shield * A valid bug but it's not high pri and doesn't align with roadmap/current focus for next release: > We're currently focusing on improvements to performance and coherence, as you can see in our pinned issue on the repo detailing our [v8 plans](https://github.com/microsoft/fluentui/issues/12770). So while we don't plan to address this right now, we will take it into consideration when we schedule future work for <component>. Thank you for reaching out to us. or > This is low priority for us as we’re currently focused on larger work items focused on performance and coherence across the library (see pinned issue on the repo). I'm going to resolve this as won’t fix but when we schedule future work on this component, we may rethink this behavior so thank you for giving us feedback - we appreciate it! > Thanks for the feedback! Currently we are focused on building out a React offering for this repo at this time. We like to hear this type of feedback from the the community and we are always evaluating what libraries to support for the Fluent Design Language. This currently isn't on our roadmap - but thanks for the feedback! * IE 11 support: > This doesn't repro on the new Edge Chromium. You can provide your own styling specific with high contrast selectors to work around this. Since this isn't a breaking issue for IE 11 and it's a minor scenario, we're not going to address this right now. * Partner vs random contributor (hard to tell sometimes) - ok to spend more time investigating and giving a codepen with workaround for partner * Feature request/backlog - set expectations: > <provide workaround if possible> I'll mark this as a feature request and add it to our backlog, but we're likely not going to get to it for a while as we're currently focused on larger coherence work items and enhancements to our performance. or > Thanks for reaching out to us. I've added this to our backlog for review but it's low on our priority list - especially since you can currently <workaround or alternate way to achieve the same behavior> * Good First Issue (ex: component not broken, examples on our docs site are) > This is a good first issue if you'd like to take a stab at it! We'll likely get to this but not for a while as it's low impact. or > It's just this example code that needs to be fixed, not necessarily a problem inside the component itself. If you're able to dig deeper into this and raise a PR, we welcome it. We're currently focused on larger worker items, around performance and coherence for V8 (see pinned issue on repo) so we'll likely not get to this for a while. Thank you for your patience. * Accessibility Issues - verify that the issue being raised is valid per ARIA spec and ask what they're citing, if not - resolution: won't fix by design. > I ran the Accessibility Insights tool on this and the ARIA label not being set on the section list doesn't get flagged as an error which makes me think that is the expected behavior, as defined by the ARIA spec. What are you citing that's expecting this? or >Can you link to the ARIA spec for the above request? Ideally from https://www.w3.org/TR/wai-aria-1.1/. It will help us triage and provide a solution. * NVDA > This component seems to following the ARIA spec correctly - I ran the Accessibility Insights tool on your codepen using our components and no errors were flagged. Though this tool doesn't flag all ARIA issues, I couldn't find any other discrepancies between the spec and this component's base code. As a result this isn't actionable on our end and looks to be a NVDA specific bug - I suggest you file an issue on their repo: https://github.com/nvaccess/nvda * Scan mode - Mark as "Resolution: External" after checking that behavior works correctly when scan mode is deactivated, especially if it relates to focusing on elements non-intended or reading things twice > I've checked our source code and it seems that we are doing everything correctly on our end and this is the behavior of opting into scan mode itself. This happens because the inherent function of scan mode is to break out of author's intent when it comes to navigation and dictation. Given all of this, I'll be marking this issue as `Resolution: External`. Thanks for filing it and let us know if there is anything else we can do to help! * Screenreader/AT problem - resolution: external > I believe this is a screenreader problem because this Textfield has all the proper ARIA properties hooked up. I ran the Accessibility Insights tool to double check and it didn't flag any errors/missing ARIA properties so it's followed the ARIA spec. So this is not actionable for us - I'm going to resolve as external. * Needs a repro > Thanks for filing this, but you'll need to add a CodePen repro before we can help. You can start from one of the [COMPONENT examples](https://developer.microsoft.com/en-us/fluentui#/controls/web/COMPONENT) (click "Export to CodePen") or https://aka.ms/fluentpen. * No reference example of this behavior out in the web.(Mark as Resolution: By Design) > I couldn't find any reference examples of <component> that has <behavior>. If you'd like you can <workaround> to achieve this behavior. This isn't something we're planning to bake into the component though. * Partner - charting/calendar/etc > Assigning <package> owner @<owner> as their team made this component. <Owner>, if you think this is a high pri issue, please suggest a fix/raise a PR. If it is not high pri or behaving as intended or not aligned with your plans for this component, please feel free to close. * Tech help/questions - direct to Stack Overflow > Thanks for the question! We're trying to grow our community over on Stack Overflow to provide answers to coding questions like this. It would be super helpful to file this on [Stack Overflow](https://stackoverflow.com/questions/tagged/office-ui-fabric-react+or+fluentui) using tags: office-ui-fabric-react, fluentui-react Thanks again for the feedback. * DetailsList/GroupedList/List (note that the bot will automatically add this to issues labeled Bug + Won't Fix + DetailsList/List/GroupedList, but you can use a variant in a custom response) > Due to the complexity and dependencies of our List components, we are actively trying to minimize risk of regressions. We sincerely apologize that we won't be able to address this issue at this moment.