Page: tabIndex default value (mainTabIndex=-1) which prevents keyboard scroll

[jcaianirh]

Describe the issue. What is the expected and unexpected behavior?
mainTabIndex=-1 as a default value prevents keyboard scroll. tlabindex should be removed. Having a tabindex on a container essentially breaks focus and keyboard scroll for all non-focusable containers below it. eg topology details side panel.

Any contributions to the main content should not have to deal with adding their own tabindex attribute to their scroll containers.

Above notes from the pr: openshift/console#9140 (comment)

workaround is to set the mainTabIndex to null.

Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.

openshift/console#9140 (comment)

Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?
Bug
What is your product and what release version are you targeting?
OpenShift 4.9

[tlabaj]

cc @jessiehuff

[jessiehuff]

Typically this tabIndex is added in order to allow for the skip to content to properly navigate to the main content area, following this WCAG item that shows this as an example. This is often required to make sure that the skip to content link works consistently across browsers. I assume that is why it defaults to -1. This article also explains it a bit. @jgiardino @seanforyou23 Do you think I missed anything? Do you see a reason that it would default to -1 if there isn't a skip to content link? (Though I highly highly suggest everyone does.)

[tlabaj]

Let's update the default value in our next breaking change release.

[thatblindgeye]

Since this has been inactive for quite a while I'm inclined to close this out. Currently we allow updating the tabindex to null in scenarios where having it set to -1 would cause issues, and I feel like the default should be that -1 value as a "skip to content" link should usually always be present. If a "skip to content" is not being implemented then there should really be a conversation as to why that is the case and whether it truly isn't needed (like Jessie said a while ago, I would also highly, highly, highly suggest one be used; I feel like it would be a rarity as to when one shouldn't be included or for very specific types of pages)

Our a11y docs for Page also include when the mainTabindex should be kept at -1.

Will leave this open a little longer in case there's continued discussion, though.