- From: Brandon McConnell via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Apr 2024 18:40:54 +0000
- To: public-css-archive@w3.org
@nattarnoff I've considered the same question. While developers could use this in either desktop or mobile, I could see developers implementing this specifically for touch devices by combining `prefers-interaction-direction` with a `pointer: coarse` check, perhaps sometimes paired with a size query as well: ```css nav { position: fixed; top: 0; } form#login { float: left; } @media (pointer: coarse) { @media (prefers-interaction-direction: bottom) and (width < 767px) { nav { top: unset; bottom: 0; } } @media (prefers-interaction-direction: right) { form#login { float: right; } } } ``` In terms of OS, prominent device companies like Google/Android and Apple would likely implement this feature exclusively on mobile and tablet devices, at least to start, unless the WCAG makes a solid argument to include it across all device types. I see a case being made for less able persons preferring most interactions to be on one side of the screen to prevent having to move the cursor so far for every interaction. Many applications will inevitably be slow to adopt this, but providing a way for applications to hook into this preference would allow those companies and developers with ample bandwidth to cater to those specific needs, which would be a great convenience to those who need it. Accessibility features like `prefers-interaction-direction` also have the potential to help companies and developers who use them. By removing unnecessary friction in the user journey, they can better serve their users and customers and increase their potential audience. -- GitHub Notification of comment by brandonmcconnell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10244#issuecomment-2075595509 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 April 2024 18:40:55 UTC