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

♿️ a11y(bal-radio | bal-checkbox): Inputs focusable #1010

Closed
1 task done
GinaBiondo-aperto opened this issue Jul 26, 2023 · 4 comments
Closed
1 task done

♿️ a11y(bal-radio | bal-checkbox): Inputs focusable #1010

GinaBiondo-aperto opened this issue Jul 26, 2023 · 4 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@GinaBiondo-aperto
Copy link
Collaborator

Current Behavior

Currently the hidden Inputs inside bal-radio and bal-checkbox are focusable additionally to the component itself. This could cause weird behavior for keyboard and screenreader users.

Expected Behavior

Only the component needed to trigger an event should be focusable

Steps to Reproduce

regular usage of radio buttons and checkboxes

Version

13.6.2

Browsers

No response

Device

No response

Code Reproduction URL

No response

Additional Information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@GinaBiondo-aperto GinaBiondo-aperto added the 🐛 bug Something isn't working label Jul 26, 2023
@hirsch88 hirsch88 added this to the ♿️ Accessibility milestone Aug 8, 2023
@hirsch88 hirsch88 changed the title a11y: fix(bal-radio | bal-checkbox): Inputs focusable ♿️ a11y(bal-radio | bal-checkbox): Inputs focusable Aug 8, 2023
@hirsch88 hirsch88 removed their assignment Mar 12, 2024
@yannickholzenkamp
Copy link
Member

/cib

Copy link
Contributor

Branch fix/issue-1010 created!

@yannickholzenkamp
Copy link
Member

yannickholzenkamp commented Sep 5, 2024

Hi @GinaBiondo-aperto

Discussed the issue in the Design-System team. According to @hirsch88 we only support the Google Chrome standard screenreader.
This issue does not seem to be present in the Google Chrome screenreader (https://chromewebstore.google.com/detail/screen-reader/kgejglhpjiefppelpmljglcjbhoiplfn?hl=de&utm_source=ext_sidebar).

Can you reproduce this issue with the Google Chrome screenreader?

We will close the issue for now. Please let us know in case we should re-open it.
Thanks!

@yannickholzenkamp
Copy link
Member

Hi @carolabes

We can't reproduce this issue with our screenreaders (see comment before).
Could you provide more information about the screenreader, browser etc. and re-open the issue in case it still exists?
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants