[marissahuysentruyt]

Description

This PR takes in the swc-tabs component (along with its subcomponents swc-tab and swc-tab-panel) in the deps directory. Now that we include two external components, we also adjusted the build for the components folder so that individual components don't have their own "build" script, but we bundle them in a dist together. After that refactoring, a small correction in the sitenav.js file was needed to update the path of the swc-tooltip.

Otherwise, this is a low-risk PR to ingest SWC tabs before implementing a tabs block in this project.

One additional fix is included to remove a hardcoded "Adobe Clean" reference that was missed in #153

Screenshots (if applicable)

Type of change

• Bug fix
• New feature / block
• Refactor
• Docs / content
• Chore (deps, config, tooling)

Related issue(s)

• partially addresses spdocs-605

Validation steps

• This PR has visual elements, so it was reviewed by a designer.
• This PR has code changes, and our linters still pass.
• This PR affects production code, so it was browser tested (see below).
• This PR affects existing pages, so automated E2E tests were run (see below).
• This PR has new code, so new tests were added or updated, and they pass.
• This PR has copy changes, so copy was proofread and approved.
• The content of this PR requires documentation, so a detailed description of the component's purpose, requirements, quirks, and instructions for use by designers and developers was added, along with accessibility information if pertinent.

To Validate

URL for testing:
https://tabs--spectrum-hub--adobe.aem.live/

• Make sure all PR Checks have passed
• Pull down the branch locally or visit the branch preview
• Run npm test and confirm all tests pass
• Run npm run lint and confirm no linting errors
• Verified in browser with aem up

Accessibility testing checklist

• Keyboard

Keyboard navigation should remain unchanged.

• Screen reader

Screen reader behavior should remain unchanged.

Device review

• Did it pass in Desktop?
• Did it pass in (emulated) Mobile?
• Did it pass in (emulated) iPad?

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• beff23c ✅ (latest)
• 8dd3e75 ✅

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/
🖥️	/

[marissahuysentruyt]

i manually checked the keyboard behavior and VoiceOver on iOS and MacOS. No repetition in the screen reader was found.