W3C home > Mailing lists > Public > www-style@w3.org > November 2015

Re: [css-snappoints] What if snapped element is much taller/wider than viewport?

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sat, 21 Nov 2015 00:04:51 -0500
To: "Belov, Charles" <Charles.Belov@sfmta.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <564FFB73.4070408@inkedblade.net>
On 11/20/2015 08:57 PM, Belov, Charles wrote:
> If a snapped element is much taller/wider than the viewport, possibly as a result of zooming by the site visitor or their personal style sheet, could the situations arise that a site visitor would miss content or would be unable to scroll down or up using the keyboard? If so, that could present an accessibility issue.
>
> Sample scenario:
> 1. Visitor presses spacebar to scroll down. Without scroll-snapping, element A would have come into view.
> 2. Browser automatically snaps to top of element A, which is three times the height of the viewport. (Will we miss content between what would have been top of screen and top of element A?  If so, this is an accessibility problem.)
> 3. Visitor presses spacebar to scroll down.
> 4. Browser automatically snaps to top of element A, which is three times the height of the viewport. (Visitor cannot escape the pull of the snap, which would also be an accessibility problem.)
>
> Does the user agent need to have an accessibility option to not snap?

This is exactly why Tab and I submitted the change proposal,
specifically this section:
   https://drafts.csswg.org/css-scroll-snap/#snap-overflow

~fantasai
Received on Saturday, 21 November 2015 05:05:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:58 UTC