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

Does the autocomplete attribute apply to the currency dropdown and Amount input fields on the transfer page? #3537

Open
ManojG-Ally opened this issue Nov 7, 2023 · 5 comments
Labels
1.3.5 Identify Input Purpose ErratumRaised Potential erratum for a Recommendation WCAG 2.1

Comments

@ManojG-Ally
Copy link

User is accessing a balance transfer page where they need to select the currency and then enter an amount in order to move funds from their account to a trust, org, etc.

In such scenarios, do we test the 1.3.5 SC?

Although we have token values listed as "transaction-currency" and "transaction-amount" in the HTML 5.2 autofill tokens
The confusion is when and where these tokens are to be used and in the above-said scenario, whether these values are applicable.

@patrickhlauke
Copy link
Member

I would actually argue that those two values have actually nothing to do per se with "information about the user", which is what 1.3.5 is scoped to. To me, it seems a mistake that they're included.

transaction-currency - The currency that the user would prefer the transaction to use
transaction-amount - The amount that the user would like for the transaction (e.g., when entering a bid or sale price)

with transaction-currency, I can almost justify it to myself that this is about the user/the user's preference, but transaction-amount really has no business being counted as "information about the user".

@alastc et al

patrickhlauke added a commit that referenced this issue Nov 7, 2023
It is hard to argue that `transaction-currency` and `transaction-amount` in any meaningful way "relate to the user of the content and pertain only to information related to that individual". (the first one, just at a stretch perhaps, but both are clearly scoped towards a specific transaction the user is carrying out)

Closes #3537
@patrickhlauke
Copy link
Member

just filed #3539

@ManojG-Ally
Copy link
Author

What if there is an Investment page where the user is investing same amount every month?

@patrickhlauke
Copy link
Member

that's not intrinsic information tied to the person though, I'd argue. it's scoped to that specific transaction, it's not something that "on any page about transactions, this is what the user will always want to invest"

@patrickhlauke
Copy link
Member

in short, to answer the original question, I would personally ignore those two transaction-* values, and argue that this is a flaw in WCAG's listing if challenged

@alastc alastc added WCAG 2.1 ErratumRaised Potential erratum for a Recommendation 1.3.5 Identify Input Purpose labels Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.3.5 Identify Input Purpose ErratumRaised Potential erratum for a Recommendation WCAG 2.1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants