Test: Verify PR preview deployment workflow

[padma012]

Title of Pull Request(PR) [REQUIRED]

The title of this pull-request should briefly summarize what it fixes or improves. Ideally 50 characters or less.

🔗 Asana, 4Help, and Related Links [REQUIRED]

Asana Ticket: [Insert link]
4Help Ticket (if applicable): [Insert link]
Other References: [PRs, notes, design files, docs]

✨ What Does This Pull Request Do? [REQUIRED]

Briefly describe the goal of this PR and what problem it solves.
For Example:
HotFix, DLP need/issue/bugfix, 4Help ticket request, etc.

🛠️ Summary of Changes [REQUIRED]

Provide an overview of the technical changes and any relevant details.
List key updates, features added/removed, or issues addressed.
For Example:
*Refactored component (X) to improve reusability
*Added feature (X) for functionality
*Removed (X) to fix (Y)

🧪 How Should PR Be Tested? [REQUIRED]

Provide detailed steps for how reviewers can test or reproduce the changes.
Step 1: ...
Step 2: ...
Expected behavior: ...

♿ Accessibility Testing [REQUIRED]

Complete standard accessibility testing and provide additional test steps/details, if applicable:

• Does this PR change anything in the front-end? This includes backend-only changes that may affect front end components (data schema changes, global configs, package version updates, etc.)

If "Yes", provide test environment details and complete or mark N/A all of the following tests:

OS/Browser/Screen reader details: For Example: macOS Tahoe 26.0.1, Google Chrome v141.0.7390.55, VoiceOver v10

• axe DevTools full/partial page scans)
• Keyboard navigability: Focus ring showing on all focusable/interactive elements in expected order, standard interaction present (keyboard testing basics)
• Screen reader comprehension: No elements hidden from screen reader, alt text, no repeated text (screen reader keyboard shortcuts)
• Color contrast at least WCAG AA (contrast checker)
• Accessible markup used (e.g., proper heading levels, labels, roles, and semantic HTML as much as possible)
• Other accessibility testing (please describe):

📝 Additional Notes

Any extra context that would help reviewers. Consider the following:
*What branch should be used for testing?
*Does this introduce new dependencies?
*Are documentation updates required?
*Could this impact existing functionality?

👥 Interested Parties

Tag any reviewers or stakeholders you'd like to include in the discussion:
@username

---

🚨[REQUIRED] - Required fields/information in the pull request