Hi @mturoci!

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@fb.com. Thanks!

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	edda4bb
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/6339452cabfdf80008ff2edd
😎 Deploy Preview	https://deploy-preview-8161--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 site settings.

⚡️ Lighthouse report for the deploy preview of this PR

I have signed the CLA:

But somehow the PR checks didn't run again. Any ideas on how to resolve this?

Edit: They ran, but some 2h later so all good.

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

@backwardok Could you take a look at https://deploy-preview-8161--docusaurus-2.netlify.app/docs/markdown-features/tabs/ and confirm if that's your desired UX?

@Josh-Cena this looks good! There's a change in behavior for keyboard-only users, but with the focus outline I think this should still be understandable on how to activate the tabs.

@mturoci Thank you for fixing this!

Hi @Josh-Cena is there anything I can do to get this PR merged in? (e.g. any required code changes)

Thanks @mturoci that looks to work as intended 👍

Was wondering, shouldn't we announce the tab content after selecting a new tab? similarly to aria-live used in #8174 ?

Let's handle that in a separate PR because I have no idea on which DOM element such attribute could be added 😅

Hi @slorber ! I wouldn't recommend announcing the tab content after selecting a new tab. As long as the user knows that the tab changed (which they should get from the change in aria-selected for the tab), they should know that the tab content should also have changed and access it when they want to.