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-checkbox, bal-radio): VO keyboard navigation not working as expected #1622

Open
1 task done
GinaBiondo-aperto opened this issue Feb 19, 2025 · 6 comments · May be fixed by #1636
Open
1 task done

♿ a11y(bal-checkbox, bal-radio): VO keyboard navigation not working as expected #1622

GinaBiondo-aperto opened this issue Feb 19, 2025 · 6 comments · May be fixed by #1636
Assignees
Labels
✨ feature New feature or request

Comments

@GinaBiondo-aperto
Copy link
Collaborator

Description of this issue

When using voice over, checkboxes and radio buttons can only be checked / unchecked with space bar but not with a combination of VO key

  • spacebar.

How to fix it

Checking should work with VO+space as well.

Code Reproduction URL

https://design.baloise.dev/?path=/story/components-form-checkbox--basic&globals=framework:html

Additional Information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@hirsch88
Copy link
Member

Hi @GinaBiondo-aperto

  1. What are VO Keys ? :-)
  2. With space only it works
  3. Event on MDN checkbox native example does not work with special key combo( like Control + Option + Space)

@carolabes
Copy link

What are VO Keys ?

It's the VoiceOver Key. VoiceOver has no separate read and form mode like other screenreader. Therefore the user needs to press a key when navigating with voiceOver. It can be capslock or control+option.

In this case, selecting with capslock+spacebar is not possible.

@mmarinkov
Copy link
Contributor

What we discussed in the last meeting 20.02.2025:

@mmarinkov mmarinkov assigned mmarinkov and carolabes and unassigned mmarinkov Feb 21, 2025
@carolabes
Copy link

I did some research and came to the conclusion that we should cover VO as well. There is almost no alternative for MacOS or iOS. Since we also test components on Windows and MacOS we should consider MacOS for A11Y.

In MDN there are native HTML elements and VO is covered there. Selecting with VO+spacebar works in MDN. For custom implementations we need to recreate native behavior so it is working like native HTML.

In conclusion we should cover the following setup:

  1. Windows: NVDA + Chrome
  2. MacOS: VoiceOver + Chrome

@hirsch88
Copy link
Member

hirsch88 commented Mar 6, 2025

/cib

@hirsch88 hirsch88 assigned hirsch88 and unassigned mmarinkov Mar 6, 2025
Copy link
Contributor

github-actions bot commented Mar 6, 2025

Branch feat/issue-1622 created!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ feature New feature or request
Projects
None yet
4 participants