[BUG] Change status of LandmarkOneMain to warning

[karanbirsingh]

Describe the bug

The LandmarkOneMain rule checks if a page has a single main landmark (no more, no less). This maps to best-practice / moderate user impact in a similar rule in axe-core. The intent is that websites shown in browsers or WebViews should have a main landmark to ease navigation. Our rule can pick up a case where a WebView is used in a larger XAML application to show a small portion of a webpage, even if the app has a XAML main landmark of its own. Determining whether a main landmark is appropriate in these different cases should be done manually and is more of an assessment-type of test. The LandmarkOneMain rule should be changed to 'warning' to reflect this.

axe-windows version 0.3.4

[karanbirsingh]

closing as LandmarkOneMain already is classified as a 'warning' instead of an 'error'. I am unable to reproduce this now, so it's likely I confused an outdated result with a current one when filing the issue