Lead: Femi Status colour Yellow title ongoing
| Table of Contents |
|---|
Description
...
Use the appropriate type depending on usage types defined above. All default browser scroll behaviours should be enabled by default. Operating sytem system and browser defaults such as scroll inertia, scroll wheel support, gesture support and any user customisations should all behave as factory designed.
...
Scroll interaction is governed by the chosen device, operatiing operating system and browser the application is running on. It is advised that those default interation interaction behaviours be unaltered primarily for conformance and accesibility accessibility reasons. Further detail and validation is offered in the 'Best practices' section below.
Best practices
For best results all default browser scroll behaviours are enabled by default. Operating system and browser defaults such as scroll inertia, scroll wheel support, gesture support and any user customisations should all behave as factory designed. For more best practices, see below.
...
Avoid scroll hijacking - Applications that implement scroll hijacking take control of the scroll and override a basic function of the web browser. Scroll hijacking is best avoided because the user no longer has full control of the page scroll and thus is unable to predict its behaviour. User’s expectation of a website’s scrolling interaction shouldn’t be destroyed for the sake of narrative experience.
...
Make sure back button works properly - When users follow a link, and then click the Back button, they expect to return to the same spot on the original page. Traditionally, using a browser’s back button will generally set the scroll position back to the previous position rather than to the top of the page. However, some modern development frameworks do not offer this functionality by default. Losing their previous position forces users to have to scroll through content they have already seen and manualy find their previous position, hence endeavour to make sure this feature is enabled.
...
Use sticky navigation - Long scrolling can make navigation problematic for users: if the navigation bar (container menu, table menu etc) loses its visibility when users scroll down, they will have to scroll all the way back up when deep within the page or table. The solution for this problem is a sticky navigation menu: it’s best to keep the navigation persistently visible, so that navigating to different areas of the app is fast and easy for users.
...
The following are the ineractions recommended and common to all.
| Input device | Discrete scroll | Continuous scroll |
|---|---|---|
| Keyboard |
|
|
| Mouse |
|
|
| Trackpad |
|
|
Best practices
For best results all default browser scroll behaviours are enabled by default. Operating system and browser defaults such as scroll inertia, scroll wheel support, gesture support and any user customisations should all behave as factory designed. For more best practices, see below.
Avoid scroll hijacking - Applications that implement scroll hijacking take control of the scroll and override a basic function of the web browser. Scroll hijacking is best avoided because the user no longer has full control of the page scroll and thus is unable to predict its behaviour. User’s expectation of a website’s scrolling interaction shouldn’t be destroyed for the sake of narrative experience.
Make sure back button works properly - When users follow a link, and then click the Back button, they expect to return to the same spot on the original page. Traditionally, using a browser’s back button will generally set the scroll position back to the previous position rather than to the top of the page. However, some modern development frameworks do not offer this functionality by default. Losing their previous position forces users to have to scroll through content they have already seen and manually find their previous position, hence endeavour to make sure this feature is enabled.
Use sticky navigation - Long scrolling can make navigation problematic for users: if the navigation bar (container menu, table menu etc) loses its visibility when users scroll down, they will have to scroll all the way back up when deep within the page or table. The solution for this problem is a sticky navigation menu: it’s best to keep the navigation persistently visible, so that navigating to different areas of the app is fast and easy for users.
Provide visual feedback when loading new content - Visibility of the system’s status remains among the most important principles in user interface design. When using the infinite scroll type, in which your app dynamically loads content, users need a clear sign that the application is doing this. Keep them informed; use a progress indicator to show that new content is loading and will soon appear on the page.
Accessibility compliance
In general each component should be A11y complied, please follow the 3 guidelines linked below.
Focus management
The scroll component itself is not keyboard focusable. Instead, it is the scrollable content area itself that is required to be focusable in order for the scroll component to work. Please see the general guidelines described in Keyboard & Focus Management Guidelines to make sure the scrollable content areas are properly supported.
Assistive scrolling bindings vary with device, operating system and browser but the key bindings described in the 'Interaction' section above should be supported as a minimum:
Screen reader support
<<Make sure the components support screen reader for content or behaviour where needed - see Screen Reader Guidelines >>
Design
| Zeplin link | Screen thumbnail |
|---|---|
 |
...