[ObjectPageSubSection]: the container of ObjectPageSubSection is focusable which violates a11y requirement

[AlexYanSap]

Reopen of #4228 (comment)

The ObjectPageSubSection should not be focusable since it's not interactive. However, it's focusable now.

You can check the sample in the sample link. and the "First Sample Form" is focusable

It's the comment from out a11y expert @anusandhanam :

Thanks for the explanation.
In our scenario, we have used the object page subsection "without" the anchor bar. ie there is only one region with some form input elements within it. Hence in this scenario the focus around the subsection region seems redundant as there is no other region above or below to arrow through. This redundancy just leads to an additional unnecessary tab stop for sighted keyboard and screen reader users.
What would you recommendation be in this scenario? Is it even recommended to use the object page subsection "without" the anchor bar?

[nikoletavnv]

Hello @AlexYanSap,
I've created an internal incident DINC0449681 to clear out the focusing behavior of the Object Page subsections. The status of the issue will be updated here in GitHub.
Regards,
Nikoleta

[IlianaB]

Hello @AlexYanSap ,
According to our ACC Keyboard specification:
The object page contains sections with information. The information can but may not contain active UI elements. For the case the
object page does not contain active UI elements the container itself is focusable and allows access to keyboard-based scrolling via
ARROW keys, PAGE UP , PAGE DOWN , SPACE and SHIFT + SPACE

Regards,
Iliana