W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

[csswg-drafts] [css-scroll-snap-1] scrolling due to focus movement should include scroll-padding (#5066)

From: Alastair Campbell via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 May 2020 12:37:42 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-617412579-1589373461-sysbot+gh@w3.org>
alastc has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-scroll-snap-1] scrolling due to focus movement should include scroll-padding ==
For keyboard/switch users who effectively tab through a page, a sticky footer (going forwards) or a sticky header (going back up the page) will obscure the view of the focused element. 

[Asking around](https://twitter.com/alastc/status/1260347064002756610), people suggested the [scroll-padding property](https://drafts.csswg.org/css-scroll-snap-1/#propdef-scroll-padding), which appears to work in Chrome but not Firefox. ([Test case](https://alastairc.uk/tests/wcag22-examples/sticky-footer3.html).)

I can't see anything on whether a browser should treat tabbing through the page as something that is affected by scroll-padding. (Although I don't read CSS specs very often, perhaps I missed it?).

Could something be added to indicate a standard behaviour for this? E.g. at the end of the [intro for 4.2](https://drafts.csswg.org/css-scroll-snap-1/#scroll-padding): "... or simply to put more breathing room between a targetted element and the edges of the scrollport. Targetted elements must also include focusable elements which gain focus when the user is tabbing through the page."

The wording is probably not appropriate for a CSS spec, but I hope you get the idea.

Co-chair, Accessibility Guidelines Working Group

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5066 using your GitHub account
Received on Wednesday, 13 May 2020 12:37:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:06 UTC