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
While fixing some accessibility issues on my companies website, I stumbled over two issues.
One comes from the Stripe element with the class __PrivateStripeElement-input:
ARIA hidden element must not be focusable or contain focusable elements
The other one from an <iframe> tag with the name __privateStripeFrame7343
Frames with focusable content must not have tabindex=-1
Solutions
To solve the first issue, the focusable content should be disabled or be removed from the DOM. There is no reason to use an aria-hidden attribute on a focusable element. -> explanation
For the second issue, the tab-index needs to be changed to not be negative. -> explanation
Additional context
The first issue was mentioned here as well but the thread was closed without it being solved.
For my company it would be crucial that is is solved because according to the European Accessibility Act, websites will legally be required to have a certain level of accessibility until end of June 2025, which includes fixing these issues.
The text was updated successfully, but these errors were encountered:
Hi @saritaSchen , thanks for the report. This is the repository for the backend Stripe SDK for Ruby; did you mean to post this in the react-stripe-js repository?
While fixing some accessibility issues on my companies website, I stumbled over two issues.
One comes from the Stripe element with the class
__PrivateStripeElement-input
:The other one from an
<iframe>
tag with the name__privateStripeFrame7343
Solutions
To solve the first issue, the focusable content should be disabled or be removed from the DOM. There is no reason to use an aria-hidden attribute on a focusable element. -> explanation
For the second issue, the tab-index needs to be changed to not be negative. -> explanation
Additional context
The first issue was mentioned here as well but the thread was closed without it being solved.
For my company it would be crucial that is is solved because according to the European Accessibility Act, websites will legally be required to have a certain level of accessibility until end of June 2025, which includes fixing these issues.
The text was updated successfully, but these errors were encountered: