#leokcw_code

1 messages Β· Page 1 of 1 (latest)

sturdy valleyBOT
#

πŸ‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

πŸ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1360072692451246080

πŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

hexed linden
#

the iframe container is getting read before the inputs
Could you elaborate a bit more here?

ripe forum
#

As an example, I tried the following:

  1. Open up the sample app above (https://7m4xjl.csb.app/) on either a Macbook (Chrome browser) or an iOS device / Android device, with a screen reader turned on (For example, VoiceOver on a Macbook, or Talkback on Android)
#
  1. Focus on one of the input fields - screen reader will read out whatever is being focused
#
  1. Attempt to navigate to the 'Next' element. This can be done on Macbook by pressing "Control + Option + Right arrow", or on a mobile device by swiping right on your screen
#

Expected Results:
3. Focus would go to the next element and read out whatever text is there

Actual Results:
3. Focus would go to the next element, but would read out what appears to be the title of the <iframe>, depending on the device.

For example, on Macbook, with the starting focus on the CVC input field, after pressing "Control + Option + Right", it'll read out "End of Secure CVC Input Frame. Group". Pressing again would read out "Secure Expiration Date Input Frame. Group". Pressing it a 3rd time would then read out "Credit or Debit Card Expiration Date MM/YY, required"

On Android, it'll be a similar issue, but it'll read out "Page Page" instead of the "Secure X Input Frame".

Playing around with it, it seems like to me that the voiceover might be focusing on the <iframe> element or some other container before eventually focusing on the <input> field within the iframe

#

Sorry, I hope it's not too confusing, let me know if there's anything I can try to clarify

hexed linden
#

Thank you for such a detailed report. Let me see if we have similar ask

ripe forum
#

Thank you!

hexed linden
#

Hi, I just found 1 ask from 2017 πŸ˜… . It looks like we haven't improved this since then unfortunately. Let me record your feedback

ripe forum
#

πŸ˜…

#

Does this mean there's currently no support for this?

#

Is there any plans on support this? Accessibility is very important to us and we're looking for a potential, alternative solution

hexed linden
#

Could you write to support and mention this Discord thread? We can follow up from there

#

I filed internally we may revisit πŸ™‚

ripe forum
#

Sure, which channel should I write to on discord?

sturdy valleyBOT
hexed linden
pallid birch
#

Hi @ripe forum I'm taking over this thread.

sturdy valleyBOT
#

Hello @ripe forum, we have sent you a direct message, please check it at https://discord.com/channels/@me/1360102840739041403

  • πŸ”—The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
pallid birch
#

@ripe forum I just send you a link through DM, you can use that link to create a ticket.

ripe forum
#

Sounds good!