[RAC 1.18.0] Switch no longer toggles on Enter — intentional change?

[Arthikumari02]

Summary

In react-aria-components@1.18.0, Switch keyboard behavior appears to have changed compared to 1.17.0, but this is not mentioned in the v1.18.0 release notes.

Specifically, Enter no longer toggles the Switch after the Switch API refactor (SwitchField + SwitchButton, PR #9877). Space still toggles, and pointer interaction still works.

I’d like to understand whether this was intentional, and whether Switch should support Enter per accessibility guidelines.

---

What changed in 1.18.0 (documented)

The release notes describe:

• New SwitchField / SwitchButton API (replacing deprecated Switch)
• Description and error message support for Switch
• Similar changes for Checkbox and Radio

There is no mention of keyboard interaction changes.

---

Observed behavior

Interaction	react-aria-components@1.17.0 (Switch)	1.18.0 (SwitchField + SwitchButton)
Click / tap	✅ toggles	✅ toggles
Space	✅ toggles	✅ toggles
Enter	✅ toggles	❌ does not toggle

---

Why I think this changed (not documented)

In 1.18.0, useToggle() was refactored so label usePress handlers ignore keyboard events (pointerType === 'keyboard'), with the comment that keyboard is handled on the input.

On the hidden input[type="checkbox"], usePress only treats Space as valid for checkbox/radio inputs — not Enter (see isValidInputKey in usePress).

In 1.17.0, Enter could still toggle via the label’s usePress handler — similar to the Checkbox behavior discussed in #6398 (“Checkbox should not be toggled with Enter key”).

So the 1.18.0 refactor seems to fix Enter-on-label for toggles generally, which removes Enter toggling for Switch as a side effect.

---

Accessibility question

The W3C APG Switch pattern lists both Space and Enter as keys that toggle a switch.

React Aria’s useSwitch docs currently describe Space only (Tab to focus, Space to toggle).

For Checkbox, Enter not toggling aligns with APG.
For Switch, APG includes Enter — so removing Enter may be a regression from an APG standpoint, even if it fixes inconsistent Checkbox behavior.

---

Questions for the team

1. Was removing Enter-to-toggle on Switch intentional in 1.18.0?
2. Should Switch support Enter per APG, while Checkbox/Radio remain Space-only?
3. Should this behavioral change be called out explicitly in the release notes / migration guide?
4. For apps on 1.17.0 that relied on Enter toggling Switch, is the recommended approach:
   • custom onKeyDown handling, or
   • waiting for a library-level fix?

[devongovett]

Supporting Enter on checkboxes/switches/radios previously was a bug. The native input type=checkbox only handles Space because Enter submits the form. #10145 (comment) IMO it's strange that switches would behave differently from checkboxes, not sure why the APG has that. The native <input type="checkbox" switch> attribute currently supported by Safari only supports Space as well.

Why is supporting Enter vs Space important for your app?

[Arthikumari02]

Thanks for the context!
I completely understand the native behavior now. I was just curious about the specific reasoning behind removing 'Enter' for checkboxes/switches/radios, as it wasn't explicitly mentioned in the documentation.