Simply not good enough

  • J

    (@sbwdblog8)


    1 month, 1 week ago

    The ability to quickly connect the plugin to a Stripe account is a big step forward (no more messing around with endpoints, hooks and manually coping and pasting code back and forth).

    Being able to quickly turn on a broad range of payment options is also useful (card, Klarna, Apple and G Pay etc).

    However, it us utterly unacceptable that a major payment gateway like Stripe is publishing software that doesn’t meet basic web standards for accessibility—particularly those relating to the visually impaired. When adding card details during the checkout the user has to type using mid-grey text on a light-grey background—how are the visually impaired supposed to see this???

    Also, the ability to style the payment section so it matches the website brand palette is nigh on impossible. Why would Stripe make the styling of fonts, colours and background elements so needlessly difficult?!

    So many basic problems.

    • This topic was modified 1 month, 1 week ago by J.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Dale du Preez

    (@daledupreez)

    1 month, 1 week ago

    Thank you for sharing your feedback and letting us know where we are falling short, @sbwdblog8.

    We actively working on how we generate the default styles for the checkout UI, and we are auditing the experience on mobile devices to improve that behaviour as well, as we realise that we need to improve in these areas. We also worked with Stripe to address a number of accessibility issues over the last few months, but this is always an area where we can (and should) continue to improve.

    Beyond all of that, it would be extremely helpful for us if you could share the site where you tested the plugin so we can better understand how we produced a poor set of styles.

    For context, we try to identify the styles in place for the current page, including input fields, and then send the styles that we detect through to the Stripe Elements code. If we ended up with grey text on a grey background, we are clearly failing, and we need to do better.

    Thanks again for letting us know that we didn’t meet your expectations. And please do share any additional details so we can do better in future.

    Piero Rocca

    (@pierorocca)

    2 weeks, 6 days ago

    Hi @sbwdblog8, thanks for the detailed feedback. Both points are valid.

    On the contrast and font rendering: you’re right that it’s not good enough. A fix is already in review that closes some gaps in how the plugin reads your theme’s colors and fonts. It should land in an upcoming release.

    On styling control more broadly: auto-detection will only ever get you so far, and you’ve put your finger on the real problem. Our sister plugin WooPayments lets merchants set colors, fonts, and border styles explicitly rather than relying on theme inference (docs here). We’re considering bringing something similar here. Would that kind of direct control solve it for you? Genuine question — it would help us prioritize it.

    One more ask: would you be willing to share your site URL so I can test the fix against your theme before it ships? Happy to flag you when it’s ready for a look.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.