You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Have Magento 2.4.6alpha2 EE setup with Venia configured.
Make sure Venia has at least one customer login account to login into the Venia front end.
Make sure Screen reader installed and enabled.
Steps to Reproduce:
Open Venia front end in any browser
Navigate by using tab button > go tops > select any product like carina cardigan
On pressing tab it should navigate to the fashion size using screen reader enabled
click and select a particular size
Expected result:
On pressing tab and selecting any size it should announce as Fashion size L button
If we select the size, then the announcement should be as Fashion size L button selected
Actual result:
On pressing tab and selecting any size it is announcing as L button
Even after selecting L size, it just says L button
DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
📖
Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.
Cypress tests in the following files did not pass 😔. All tests must pass before this PR can be merged
user should be able to add and remove promotions from cart:
AssertionError: Timed out retrying after 30000ms: Expected not to exist in the DOM, but it was continuously found.
user should be able to update their address book:
CypressError: Timed out retrying after 60000ms: `cy.wait()` timed out waiting `60000ms` for the 1st request to the route: `gqlSignInAfterCreateMutation`. No request ever occurred.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
glo82145
changed the title
RaghavendraTirumalasetti
added
the
accessibility
…ns related to size
Description
Pre-Conditions:
Have Magento 2.4.6alpha2 EE setup with Venia configured.
Make sure Venia has at least one customer login account to login into the Venia front end.
Make sure Screen reader installed and enabled.
Steps to Reproduce:
Open Venia front end in any browser
Navigate by using tab button > go tops > select any product like carina cardigan
On pressing tab it should navigate to the fashion size using screen reader enabled
click and select a particular size
Expected result:
On pressing tab and selecting any size it should announce as Fashion size L button
If we select the size, then the announcement should be as Fashion size L button selected
Actual result:
On pressing tab and selecting any size it is announcing as L button
Even after selecting L size, it just says L button
Related Issue
Closes #https://jira.corp.adobe.com/browse/PWA-3063.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist