You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the snap-strictness section the spec talks about how different screen sizes can prevent content from being accessible. When users with low vision zoom in they end up with scaled content between breakpoints and often content is pushed off the bottom of the screen but when the user scrolls the viewport is moved to the next snap position and the low vision users can't access all of the content. We need an inclusive solution.
The text was updated successfully, but these errors were encountered:
The solution is to only use mandatory snapping when you are using it on elements that collectively cover the total page content, so that you trigger the rules in https://www.w3.org/TR/css-scroll-snap-1/#snap-overflow when necessary. E.g. use it on SECTION and not on H3. Or use proximity snapping instead of mandatory snapping. This is already described in the spec.
Might be nice to see some mention of browser zoom or mention of people with disabilities this might impact in the document so people are aware of the impact between breakpoints and not just at fixed breakpoints.
In the snap-strictness section the spec talks about how different screen sizes can prevent content from being accessible. When users with low vision zoom in they end up with scaled content between breakpoints and often content is pushed off the bottom of the screen but when the user scrolls the viewport is moved to the next snap position and the low vision users can't access all of the content. We need an inclusive solution.
The text was updated successfully, but these errors were encountered: