- From: David Fazio via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jan 2022 03:17:06 +0000
- To: public-css-archive@w3.org
Use case for "wide" scrollbar UA setting = Author understands that users with learning and cognitive disabilities need to be able to understand what things are and how to use them, as referenced in How To Make Content Usable For People With Learning and Cognitive Disabilities Guide (pasted below). COGA users need to understand that the page is not showing all available content on the screen, let's say financial transaction bank account data for example. The page has more content if, and only if, the user scrolls down to view it. Understanding that additional content exists, by scrolling, is predicated on the presence of a visual indicator, most commonly the scroll bar. However, a thin scroll bar can be easily hidden from view due to neuropsychological phenomenon's commonly exploited by magicians, that also effect how we navigate content (in-attentional blindness, visual masking, etc.). The overwhelming amount of content on the screen makes the sliver thin scroll bar impossible to notice. Worse than that, it is intelligible because it's so thin it looks like it's possibly just part of the frame. In any case, the author knows that this is an important part of the user experience for the customer to have cognizance of what information is available to them, but just what exactly is an appropriate standardized width to effectuate this understanding? Having an available setting provides them with a consistent implementation, giving the user confidence to navigate their account across platforms. 4.2 Objective 1: Help Users Understand What Things are and How to Use Them Users with cognitive and learning disabilities may have trouble with orientation and learning. This can mean people get disoriented in a site. Learning new things and remembering new information is especially difficult for people with cognitive and learning disabilities. They can also struggle or be unable to learn new design patterns. Make controls, icons and elements simple and conventional to help. Make it clear to users what things are and how to use them. This includes clearly indicating the purpose of: a site, section of a site, page, section of a page, and controls. Use headers, labels, and other signposts to help users know the purpose of the page, region, or control. Help users understand how to use controls and elements on each page. Use familiar design patterns, terms, and icons to help users who struggle to remember new designs. Ensure the look, location, and interaction of controls and other elements are familiar and consistent across the site. Show a clear relationship between controls and the content they effect to help users understand the effect of possible actions and reduce potential confusion. -- GitHub Notification of comment by Helixopp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6351#issuecomment-1011741964 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 January 2022 03:17:08 UTC