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

Getting accessibility issue using JAWS screen reader when using recaptcha v2 sitekey #291

Closed
harish-byralingaiah opened this issue May 20, 2023 · 6 comments
Labels

Comments

@harish-byralingaiah
Copy link

Hello Team,

When using tab key in JAWS screen reader recaptcha checkbox is reading the complete IFRAME URL instead of saying checkbox but same is working using arrow keys for navigation.

"ng-recaptcha": "^5.0.0"
Angular cli: 14

@harish-byralingaiah
Copy link
Author

We are using recaptcha V2 site key. Kindly help.

@harish-byralingaiah harish-byralingaiah changed the title Getting accessibility issue using JAWS screen reader Getting accessibility issue using JAWS screen reader when using recaptcha v2 sitekey May 20, 2023
@harish-byralingaiah
Copy link
Author

harish-byralingaiah commented May 21, 2023

We have tried with latest version 10.0.0 compatible with Angular 14, even after the issue persist. Kindly need your immediate response on this as we have production release early next week.

Even this example is having issue with jaws
https://dethariel.github.io/ng-recaptcha/basic

@DethAriel
Copy link
Owner

hi @harish-byralingaiah ! Do you have a proposal on how this issue can be fixed?

@harish-byralingaiah
Copy link
Author

harish-byralingaiah commented May 22, 2023

Hi, I tried to add a title and aria-label to re-captcha element, but after doing so, it reads the tile and aria-label first, followed by the Iframe URL. So I am not able to find a solution for this.

@harish-byralingaiah
Copy link
Author

Hi, can the role="presentation" from the iframe be removed?

@DethAriel
Copy link
Owner

@harish-byralingaiah the iframe parameters are not under the control of ng-recaptcha. I would suggest that you consider bringing awareness to this issue in the main recaptcha project: https://github.com/google/recaptcha

Since this issue is not fixable in ng-recaptcha, closing this ticket as invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants