Matt Lacey
Matt Lacey
What can be done to help developers produce more accessible XAML? Ideas include missing AutomationProperty tags. Need to establish, rules for adding these though and then look at what else...
Don't put a ViewCell in a Carousel https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/carouselview/populate-data > When using CarouselView, never set the root element of your DataTemplate objects to a ViewCell. This will result in an exception...
If a WebView is inside a StackLayout, ensure WidthRequest and HeightRequest are set https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/webview?tabs=windows > It may be necessary to set the WidthRequest and HeightRequest properties of the WebView to...
To aid accessibility in the final app, there are probably things that can be detected at design time as possible addressable issues. Initially thinking about the narrator, but other accessibility...
**NEEDS FULLY SPECIFYING** Manually creating design-time data is more effort than it feels like it should be. - What can be done to make it easier, automate it, or generate...
Because some user-initiated actions (e.g. generate XAML, and analyze current document) may take time, look at using an `IVsThreadedWaitDialog4` to provide user feedback while actions are taking place. See code...
See control list from https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/#alphabetical-index
It's possible to change/suppress analysis error types with the `settings.xamlanalysis` file but this requires an entry for each code. It is desirable to suppress multiple similar codes without having to...
Tab elements should always have `Title` and `Icon` attributes set. error type = warning
**Is your feature request related to a problem? Please describe.** **Describe the solution you'd like** **Describe alternatives you've considered** **Additional context**