Fix accessibility errors on cart and checkout pages

[vovayatsyuk]

Description (*)

This PR fixes Accessibility errors reported by Lighthouse module (Available in Chrome dev tools) on the shopping cart and checkout pages.

Manual testing scenarios (*)

1. Open Stores > Configuration > Sales > Sales > Gift Options and enable gift messages for both orders and per item levels.
2. Add product to the cart.
3. Navigate to the shopping cart page and run the Lighthouse accessibility test. There is an "ARIA IDs are not unique" error.
4. Navigate to the checkout page and run the Lighthouse accessibility test. There are navigation and ARIA errors.
5. Apply the patch and check the pages again.

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)

Resolved issues:

1. resolves [Issue] Fix accessibility errors on cart and checkout pages #34483: Fix accessibility errors on cart and checkout pages

[m2-assistant]

Hi @vovayatsyuk. Thank you for your contribution
Here are some useful tips 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

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ihor-sviziev]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[Den4ik]

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE, Unit Tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ihor-sviziev]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ihor-sviziev]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[vovayatsyuk]

@magento run Functional Tests CE

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-9188 has been created to process this Pull Request
✳️ @ihor-sviziev, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[magento-engcom-team]

Hi @Den4ik, thank you for the review.
ENGCOM-9188 has been created to process this Pull Request
✳️ @Den4ik, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[engcom-Alfa]

@magento give me test instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Alfa, here is your Magento Instance: https://e46915b5399fbfc31ecc6b6711e7dcca.instances.magento-community.engineering
Admin access: https://e46915b5399fbfc31ecc6b6711e7dcca.instances.magento-community.engineering/admin_92a2
Login: e5e44cd4
Password: f4a2e91c2bb2

[engcom-Alfa]

@magento create issue

[engcom-Alfa]

✔️ QA Passed

Preconditions:

1. Have a Magento installed with Sample data

Manual testing scenario:

1. Open Stores > Configuration > Sales > Sales > Gift Options and enable gift messages for both orders and per item levels.

2. Front end: Add product to the cart.

3. Navigate to the shopping cart page and run the Lighthouse accessibility test; Validate the result.

4. Navigate to the checkout page and run the Lighthouse accessibility test; Validate the result.

Before: ✖️ Shopping cart checkout pages were giving an "ARIA IDs are not unique" error with ~90% accessibility result and Checkout payment page were with navigation and ARIA errors.

After: ✔️ Shopping cart checkout pages are with 100% accessibility result without errors and Checkout payment page also with 98% without navigation and ARIA errors.

Since this fix relevant to accessibility result fix and has no impact on functional regression, there is no additional testing is required on this!