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
The inline error message is not focused and is not announced when a user enters an invalid card number or expiry date.
The VO announced “Error: Invalid input“ for the field when the user navigates back to the card number or expiration date field with the left swipe gesture.
The trait (Button, Double-ta to activate) is not announced for the VO of “Pay“ CTA.
The focus is not moving to the error message after double tap on Pay CTA (This issue observed for all the error states like, expiry card, Incorrect CVC, card_declined_on_card_add).
Listen to the VO of the different elements on the screen
Enter a cc decline card (4000000000000002) and try to submit. Listen to the VO
Expected behavior
After double tapping on checkout, the focus and VO should be moved to the Payment sheet, not on the background screen.
The VO for the Pin/Zip code field data should be announced in single separated digits (9 8 1 0 1) not in words (ninety-eight thousand one hundred one).
The inline error message should be focused and announced asap when a user enters an invalid card number or expiry date.
When the user navigates back to the card number or expiration date field with the left swipe gesture, the VO of the inline error message should be announced exactly as it is displayed along with the value that is “Edit box: 424242… Card number. Your card number is invalid“ not the “Edit box: 424242…Card number. Error: Invalid input“.
The trait (Button, Double-ta to activate) should be announced for the VO of “Pay“ CTA.
The focus should move to the error message after double tapping on Pay CTA. (for all the error states like, expiry card, Incorrect CVC, card_declined_on_card_add).
Screenshots
See videos
Smartphone:
Device: Samsung Galaxy F15 (14)
OS: Android
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Video- 1-VID20240718135805.mp4
Video- VID20240718140202.mp4
Video- VID20240718140448.mp4
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
See videos
Smartphone:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: