Bug - Skip to content - focus remains at top of page in demos

[thatblindgeye]

Describe the problem
Followup based on comment #7520 (comment)

The skip to content component has a bug in demos where when you click it, focus remains at the top of the page/the page does not scroll to the main content.

How do you reproduce the problem?

1. Go to skip to content React demo
2. Press Tab to place focus on the Skip to content button, press Enter, then press Tab again. Notice that focus goes back to the skip button, and the page did not scroll to the main content.
   • If you click anywhere on the page first then follow the steps above, the page does scroll to the main content, but focus still remains at the top of the page when pressing Tab again
3. Go to bulk select table demo and repeat Step 2, and notice the same behavior.

Expected behavior
The skip to content in React demos should have the same behavior as seen in the skip to content HTML demo

Additional notes

Possibly an issue with routing? Noticed when testing something via VO in Safari that the page does scroll to the linked content area, but then immediately returns to the top of the page.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[thatblindgeye]

For additional context, this isn't a bug with only Skip To Content demo(s). Testing a full screen Page demo, clicking the SkipToContent with keyboard and then pressing the Tab key, the SkipToContent button receives focus again instead of the next focusable element within the "main content".

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.

[rebeccaalpert]

Still an issue in 6!