Allow Lighthouse scan to reach 100% Accessibility on Homepage

[Serfe-com]

Description (*)

We adjust the rendering of the menu and small adjustment on the contrast for the page to allow to hit 100% on accessibility on the home, PDP y PLP on Luma

Related Pull Requests

38617

Fixed Issues (if relevant)

1. Fixes Lighthouse Accessibility failure #39054
2. Fixes Accessibility: WAI-ARIA roles nesting wrong in menu #35889

Manual testing scenarios (*)

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

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

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

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

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.

[Serfe-com]

@magento add to contributors team

[m2-assistant]

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

[Serfe-com]

@magento I am working on this

[Serfe-com]

@magento I am working on this

[Serfe-com]

@magento run all tests

[Serfe-com]

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

[magento-deployment-service]

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

[magento-deployment-service]

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

[Serfe-com]

@magento run all tests

[Franciscof-Serfe]

@magento run all tests

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @Serfe-com,

Thanks for the contribution!

Please fix the failed static tests.

Thanks

[Franciscof-Serfe]

@magento run all tests

[Serfe-com]

@magento run all tests

[Serfe-com]

@magento run all tests

[engcom-Hotel]

@magento run all tests

[engcom-Bravo]

@magento run all tests

[engcom-Bravo]

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.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Functional Tests EE

[engcom-Dash]

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

[Franciscof-Serfe]

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

[engcom-Dash]

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