Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Lighthouse scan to reach 100% Accessibility on Homepage #39164

Open
wants to merge 6 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

Serfe-com
Copy link

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)

Copy link

m2-assistant bot commented Sep 12, 2024

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.

@m2-community-project m2-community-project bot added the Priority: P3 May be fixed according to the position in the backlog. label Sep 12, 2024
@Serfe-com
Copy link
Author

@magento add to contributors team

Copy link

m2-assistant bot commented Sep 12, 2024

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

@Serfe-com
Copy link
Author

@magento I am working on this

@Serfe-com
Copy link
Author

@magento I am working on this

@Serfe-com
Copy link
Author

@magento run all tests

@Serfe-com
Copy link
Author

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

@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Sep 13, 2024
Copy link

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

Copy link

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

@Serfe-com
Copy link
Author

@magento run all tests

@Franciscof-Serfe
Copy link
Contributor

Franciscof-Serfe commented Oct 14, 2024

@magento run all tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Priority: P3 May be fixed according to the position in the backlog. Progress: review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Lighthouse Accessibility failure Accessibility: WAI-ARIA roles nesting wrong in menu
2 participants