[usePress]: usePress print virtual click when not opening voiceover

[theniceangel]

Provide a general summary of the issue here

When I open system settings like follows:

Then, I tap on this button,

sometimes it will print virtual click

🤔 Expected Behavior?

Should always print mouse

😯 Current Behavior

Sometimes print virtual

💁 Possible Solution

No response

🔦 Context

No response

🖥️ Steps to Reproduce

Directly visit https://react-spectrum.adobe.com/react-aria/usePress.html

Version

The official website

What browsers are you seeing the problem on?

Chrome

If other, please specify.

Chrome Version 131.0.6778.205 (Official Build) (arm64)

What operating system are you using?

Apple M1 Pro, Sequoia 15.2

🧢 Your Company/Team

No response

🕷 Tracking Issue

No response

[devongovett]

What real-world issue does this cause for you?

[theniceangel]

I need to distinguish whether the user triggered the action using a mouse or by enabling VoiceOver and using Control + Option + Space. If the action is triggered with Control + Option + Space, it is considered a virtual event, and I treat it as a keyboard operation. I executed some logic and if performed by mouse, I need do another logic.

[snowystinger]

Can you provide more specifics? In general you shouldn't be taking different actions for VoiceOver press vs Keyboard press. It increases the likelihood of divergence in behaviour making it harder to ensure that all users can do all the same tasks.

Maybe there is something else we should be exposing/doing though, but we don't know without more information.

[snowystinger]

Linking possibly related issues
#6165
#6207
#3819
There's definitely some funniness going on with tap to click, not sure what our umbrella issue should be for it yet.