fix(theme): remove superfluous ARIA region from SkipToContent link

[JoshuaM195]

Removes the <div role="region"> wrapper around the skip-to-content link. Screen readers were announcing the element twice: once for the region landmark and once for the link itself, e.g. "skip to main content region, link, skip to main content".

The ref used for page-transition focus management is moved directly onto the <a> element, eliminating the need for the wrapper div entirely.

Fixes #8418

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Fixes #8418
The SkipToContentLink component wrapped the skip link in a <div role="region" aria-label="Skip to main content">. This caused screen readers to announce the element twice. Once for the landmark region and once for the link itself, e.g.:

"skip to main content region, link, skip to main content"

A skip link does not need to be a landmark region. It should be a bare <a> element.

Changes

• Removed the <div role="region" aria-label={...}> wrapper from SkipToContentLink
• Moved the focus-management ref directly onto the <a> element (renamed containerRef => anchorRef, type updated to HTMLAnchorElement)

Test Plan

• Tested with a screen reader (NVDA + Firefox): the skip link is now announced as "Skip to main content, link" with no duplicate region announcement.
• Clicking the skip link still moves focus to <main>.
• Page navigation still refocuses the skip link correctly.

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[meta-cla]

Hi @JoshuaM195!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d28c925
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/69dee6e380b7d40009089a87
😎 Deploy Preview	https://deploy-preview-11938--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!