#Roman Usherenko-card-element

1 messages · Page 1 of 1 (latest)

obsidian monolith
#

That's an interesting point. Do you have a screenshot of the element in the browser dev tools that we can look at?

vernal tree
obsidian monolith
#

Is that page locally hosted? Or is it accessible via a URL I can look at?

vernal tree
#

hmm, so this is calendly. lemme see if i can craft a link for you

obsidian monolith
#

Awesome thanks!

vernal tree
#

ah wait. you won’t see it there

#

so, we’re actually fixing this “on the fly” by adding a tabindex=-1

#

so in this link that i’ve sent you everything is ok because of that. but i’d like to remove this back in favor of having this fixed in your side

mental magnet
#

Hello, two-shoes had to step out but I am helping look in to this. My memory is fuzzy on the details so I will have to look it up, but from what I remember we made sure to code to mitigate the negative effects of that violation

#

Was your page working incorrectly with a certain screen reader or something?

vernal tree
#

it was failing the automated axe check that we have as a part of our test suite

#

you can see that if you install axe devtools extension, remove the tabindex=“-1” that we’re adding, and run the full page scan

mental magnet
#

Gotcha, thanks for the clarification. Apologies I am getting sidetracked on other questions but I am looking in to this now and will get back to you shortly. I definitely remember Stripe.js triggering automated test failures before but again I think we mitigated the actual behavior, just not in a way that those catch.

#

Unfortunately I'm not finding external docs on this but we have accounted for this. Automated testers still flag that as an issue but we consider it to be a false positive. We need this to be focusable so that users that use screen readers can input their card details. To still ensure keyboard and screen reader accessibility, we use hidden input fields and logic to forward the focus from the hidden input field to the hosted field.

vernal tree
#

yes, i can see that. the issue is that hidden field is still technically possible, which it should not be if it’s a hidden input

#

setting the tabindex to remove it from the tab-sequence fixes this

mental magnet
#

Would you mind writing in a quick email about this to our support team? https://support.stripe.com/?contact=true

Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

#

If you can do that and DM me your email, I can grab that ticket and raise this to the devs that work with Stripe.js for the fix

vernal tree
#

sure thing!

mental magnet
#

Thank you, I deleted the message with your email as bots sometimes scrape public servers, but I can grab your ticket and escalate from there. Thanks for the report!