Default extension scroll behavior can lead to inaccessible content for keyboard-only users
See original GitHub issueDescribe the bug
In #1269 we found that a guidance page in the extension with no interactive links fails the scrollable-region-focusable rule. Because overflow
is not set on insights-root
, it is possible for a scrollbar to appear only over the main landmark div excluding the header. When a keyboard-only user tabs to the page, focusing on the body may not be sufficient to scroll the page with the arrow keys. However, if either:
- there are any interactive elements that receive tab focus, or
- the scrollable content is focusable
- the scrollable content is the entire body
scrolling is possible via the keyboard.
We should explore how to structure our default guidance page (and other pages in the extension as well) to ensure they are fully accessible.
To Reproduce Steps to reproduce the behavior:
- Go to any guidance page, such as the “How to test” pages in the launchpad
- Remove any interactive links via code or devtools
- Try to scroll the page with the keyboard only
CodePen repro example
https://codepen.io/karansin/pen/VwZgaxR
Expected behavior
The user should be able to scroll content with the arrow keys only.
Extension (please complete the following information)
- OS: Windows
- Version 2.9.2
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
scroll-behavior - CSS: Cascading Style Sheets - MDN Web Docs
The scroll-behavior CSS property sets the behavior for a scrolling box when scrolling is triggered by the navigation or CSSOM scrolling APIs ...
Read more >Links - Usability & Web Accessibility - Yale University
Users can speak the text of the link that they would like to follow. Keyboard-only users may not be able to use a...
Read more >IBM accessibility requirements
This page lists the accessibility requirements that need to be met for recent releases of several standards and regulations. IBM teams are required...
Read more >Proposed Scrollable element is keyboard accessible
This rule checks that scrollable elements can be scrolled by keyboard ... these guidelines will also often make Web content more usable to...
Read more >Voluntary Product Accessibility Template (VPAT)
Users of the JAWS screen reader might experience the following bug: Sorting a table may result in incorrect row headers being announced. We...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ferBonnin There would be no need for scrollbar if the content is not large enough for the view port and this rule would pass.
Even the current failure occurs only when the view port is so small that a scrollbar is needed to view all the content
validated in insider. looks good.