- From: Lisa Seeman <lisa1seeman@gmail.com>
- Date: Thu, 20 Jan 2022 20:06:19 +0200
- To: Janina Sajka <janina@rednote.net>
- Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, Matthew Atkinson <matkinson@tpgi.com>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
- Message-ID: <CAKExBMJy_LtZsTY+AE2H7Y4VttJgo+TsnQu7BU8YyeBro5Moaw@mail.gmail.com>
Hi We discussed this onthe call with regard https://drafts.csswg.org/css-scrollbars-1/ I think we would like the notes to included warning for reduced accessibility and useability, especially for people with low vision and or people with learning and cognitive disabilities for: - making the scroll bar thin or none - reducing the contrast of the scroll Useability testing should included these user groups, when reducing the size or contrast of scrolls bars Also we would like to mention that double or nested scroll bars is often an accessibility issue and they should be avoided. If they are necessary there should be very clearly grouped with the related content, so that users can clearly tell what content will be affected by what scroll bar. Does this wording work for everyone? All the best... Lisa On Thu, Jan 20, 2022 at 4:37 PM Janina Sajka <janina@rednote.net> wrote: > Hi, Lisa: > > Thanks for including the APA Co-Chairs in your email. However, I think > we need to do a bit more to properly coordinate spec reviews, so I have > added the APA list in this response. As you know, and COGA participants > should be told, horizontal review is APA's responsibility. To that last > point most specifically it seems you're revisiting an issue already > resolved by APA. In fact that resolution took a joint teleconference > with CSS. > > While we welcome COGA input, we need that input coordinated with APA's > activity, not independently pursued. I would certainly like to avoid > formalizing how we go about performing horizontal reviews, but we should > not be reopening issues recently closed without coordination. > > With that in mind, a couple comments below ... > > Lisa Seeman writes: > > Hi Folks > > > > I took and action to review CSS scroll at > > https://github.com/w3c/csswg-drafts/issues/6351 > > > > Having scroll this or removing the sroll bar on scrollable object will > make > > it unusable for many people > > > I'm having trouble understanding your statement, Any chance of a plain > language version of this sentence? > > > Also having low contrast color will also reduce accessibility. > > > Where do you see the CSS spec promoting (or requiring) low contrast? > > Best, > > Janina > > > Controls should be clearly associated with the section they control. This > > is not possible when you can not see them. > > > > relevant parts of content usable for reference: > > > > > > 4.3.1 Make it Easy to Find the Most Important Tasks and Features of the > > Site > > 4.3.4 Make it easy to find the most important actions and information on > > the page > > > > 4.2.6 of content useable is important > > <https://www.w3.org/TR/coga-usable/#what-to-do-4> > > > > The relationship between controls and affected content should be > completely > > clear and unambiguous. > > > > This can be achieved through: > > > > - visually grouping controls with the content they relate to, > > - including controls within the region they affect, > > - using clear dividers or white space between regions in a page that > may > > have separate controls or a scroll bar, > > - avoiding multiple or nested scrolling areas. > > -- > > Janina Sajka > (she/her/hers) > https://linkedin.com/in/jsajka > > Linux Foundation Fellow > Executive Chair, Accessibility Workgroup: http://a11y.org > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa > >
Received on Thursday, 20 January 2022 18:08:14 UTC