Lead: Femi Status colour Yellow title ongoing
| Table of Contents |
|---|
Description
...
Scroll interaction is governed by the chosen device, operating system and browser the application is running on. It is advised that those default interaction behaviours be unaltered primarily for conformance and accessibility reasons.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.
...
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 As our recommendation is the use of the native browser scrollbar component, screen reader support is already built in. Users are notified about the existence of a scrollbar on the page when they encounter a scrollable area with the 'overflow' property defined as 'auto' or 'scroll'. Make sure the scrollable area itself also supports screen readers for content or behaviour where needed - see Screen Reader Guidelines >>
Design
| Zeplin link | Screen thumbnail |
|---|---|
 |
...