-
Notifications
You must be signed in to change notification settings - Fork 125
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
[Accessibility] Payment methods should be radio options #1695
Comments
Hey @gazjoy , Thanks for getting back to us with these accessibility issues. Can you also share what version of the SDK are you using during your tests? |
And, as mentioned in #1691 (comment), this is also something we expect to be reported on in our ADA / WCAG accessibility review |
version is: "@adyen/adyen-web": "5.22.0" |
A fix for this has been released in the newer version |
@m1aw Hi is there any update on when these will be made into radios? Thank you. |
Hey @gazjoy yeah. We are going forward with this in v6. We do not have a release date yet, but I we are thinking in the next 1-2 months. |
Hi @m1aw |
We are now targeting the first few months next year, tho this is a concrete date. One question, does the current solution not solve the problem? Because the list is correctly marked with the appropriate role. |
Describe the bug
As part of WCAG 2.1 - 1.3.1: Info and Relationships the payment methods should give meaning of their relationship to each other. This is because they are separate buttons with no relationship. This is important as giving the methods a mutually exclusive relationship means a screen reader user will understand there are options for the method of payment. We only want to give users one option but also describe to the user that options are available. input type="radio" does this. At the moment the only way for screen reader users to understand options are available is to jump forward and backwards in the document. They could easily miss the fact that they could pay with PayPal or any other option.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Users should be able to understand they can use their credit card or another means. When navigated to by a screen reader I would expect to hear:
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: