Potential Incorrect Failure Examples in "Scrollable Content Can Be Reached with Sequential Focus Navigation" Rule

[vartikapandey53]

Hi Team,

I was reviewing the failed examples for the "Scrollable content can be reached with sequential focus navigation" rule and noticed that the provided examples may actually be passing the rule's definition.

Failed Example 1 (overflow-y: scroll;)
This example appears to allow keyboard users to navigate to and interact with the content inside the scrollable region.
Failed Example 2 (overflow-y: auto;)
Similarly, content within this example is reachable via sequential focus navigation.

Since both cases maintain keyboard accessibility, could you confirm whether these are indeed valid failures?

[JAWS-test]

Until recently, scrollable areas were only automatically focusable and scrollable with the keyboard in Firefox. This now also works in Chrome and Edge. I have not checked other browsers. If all browsers support automatic scrolling of these areas with the keyboard in the future, the examples in this ACT rule can be adapted.

[patrickhlauke]

https://adrianroselli.com/2022/06/keyboard-only-scrolling-areas.html

[vartikapandey53]

Thank you for the clarification. If the failed example is passing in most modern browsers (Chrome, Edge, Firefox) and only failing in Safari, then this should be explicitly noted rather than marking it as a general failure.

• As per Adrian Roselli's article, Safari does not fully support keyboard-only scrolling for overflow containers, while other major browsers have improved support.
• Chrome (since v105+) and Edge now allow scrolling focusable overflow containers using arrow keys, aligning with Firefox's long-standing behavior.
• The failure condition is now browser-specific, not a general WCAG failure.

I propose adding a note specifying browser discrepancies instead of listing this as a universal failure. This ensures clarity while acknowledging the existing limitations in Safari.