search

dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
21.99k stars 1.72k forks source link

Add an alternate style for desktop / mouse #13098

Open mattleibow opened 1 year ago

mattleibow commented 1 year ago

Description

Currently the styles in the templates are great for mobile, but in a complex desktop app the buttons and items are quite large.

It would be great to have a style that is mouse-first.

Public API Changes

None.

Intended Use-Case

Create more dense UIs for mouse-only.

mattleibow commented 1 year ago

@rachelkang when you were doing the themes for the templates, did you see any desktop mode for the a11y checkers? I know all the things need to fit all fingers, but for button sizes was there like a limit that would fail the checks even if you want to add more stuff?

Also, I know WinUI had 3 styles, compact, normal and expanded/touch... maybe we need that too?

rachelkang commented 1 year ago

Accessibility Insights can be run on Windows (as well as Android, which frankly is where I have used it more) so we can definitely experiment with the different styles and minimum sizes.

As helpful as the tool is though, it doesn't capture everything, so it's best to check out the Microsoft Accessibility Standards, which is inclusive of WCAG and other standards.

According to WCAG 2.1, 44px was the minimum target size https://www.w3.org/WAI/WCAG21/Understanding/target-size.html, which is what the tool reflected, and which is why we have that minimum in our styles

But interestingly, I'm seeing now that in WCAG 2.2, 22px is the new minimum target size https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html (??? It seems a bit backwards to me - fyi @PureWeen)

Regardless of my opinion, if we want to pursue smaller sizes for any reason, we should check with MAS internally to see what the recommended approach is.

ghost commented 1 year ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

lfmouradasilva commented 1 year ago

Any updates on this issue?