Hi @Serfe-com. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@magento add to contributors team

Hi @Serfe-com! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@magento I am working on this

@magento I am working on this

@magento run all tests

https://github.com/magento run all tests

Hi @Franciscof-Serfe. Thank you for your request. I'm working on Magento instance for you.

Hi @Franciscof-Serfe, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

@magento run all tests

@magento run all tests

@magento run all tests

@magento run all tests

@magento run all tests

@magento run all tests

@magento run all tests

Hi @Serfe-com,

Thanks for the collaboration & contribution!

✔️ QA Passed

Preconditions:

• Install fresh Magento 2.4-develop

Steps to reproduce

• Load the website on the homepage with Luma
• Trigger a lighthouse scan enabling the accessibility scan.

Before: ✖️ 

After: ✔️

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

@magento run all tests

@magento run Functional Tests B2B, Functional Tests EE

For Functional B2B the consistent test failure is the known issue and Jira raised for the same. Hence moving this PR to Merge in Progress.

Build 1:
Function Tests B2B: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39164/16bce3e6831e77179906ff3f93fed8c1/Functional/allure-report-b2b/index.html#categories/45dbe0d46e96664d663d093b248a272b/a09f89b84515f9bf/

Build 2:
Functional Tests B2B: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39164/3cc4d7ab0fe5ad32fa3affac5070c15e/Functional/allure-report-b2b/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Known Issue: AdminValidateMixedNestedCategoryInWidgetTest ACQE-7641

Hi Team, @engcom-Bravo @engcom-Dash @engcom-Hotel,

Would it be appropriate to label this PR as Progress: ready for testing if it has already been tested?

I've noticed that in other PRs, the Progress: accept label is applied after the Ready for Testing stage.

Could you confirm if this is the correct status?

Thank you!

Best regards,
Francisco

Hi @Franciscof-Serfe We were facing some challenges with bot. I have updated the correct labels now. Thank You!!

Noticed a small problem with the pr. The pr removes data-role="content" from the content elements, but the tabs.js uses by default a selector [data-role=content] to hide the content elements when they're not active. The end result is not pretty