[Textbox] - onClick handler is still being passed when the component is disabled

[sianford]

Description

When the component is disabled, NVDA screen reader registers that the input field is clickable with a mouse/trackpad.

Reproduction

https://carbon.sage.com/?path=/story/textbox--disabled

Steps to reproduce

1. Open the Textbox Disabled story in Windows.
2. Open NVDA with the Speech Viewer switched on.
3. Click on the content of the disabled Textbox field.
4. Inspect the Speech Viewer window.

Expected result:
There is no response when the field is clicked on. This is not accessible at all using the keyboard (which is expected behaviour).

Actual result:
The Speech Viewer states the field is "clickable".

JIRA ticket numbers (Sage only)

SKPU-11421

Suggested solution

Remove the onClick handler for disabled inputs.

Carbon version

132.1.0

Design tokens version

No response

Relevant browsers

Firefox, Chrome, Microsoft Edge

Relevant OSs

Windows

Additional context

VoiceOver used with Safari on Mac also states "To enter text in this feild, type." indicating it also detects the field is accessible.

Confidentiality

• I confirm there is no confidential or commercially sensitive information included.

[edleeks87]

We are still passing a handler to the underlying input, we should add a ternary like we have in Textbox to solve this

[edleeks87]

FE-6430

[stale]

This issue has been automatically marked as stale because it has not had recent activity. If you believe this issue is still valid and required please comment below. It will be reviewed by the core Carbon team and may be closed if no further activity occurs. Thank you for your contributions.

[carbonci]

🎉 This issue has been resolved in version 154.4.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀