Repository navigation
[a11y][Chip] Clickable always assigned to component #49511
Description
Steps to reproduce
Steps:
- Open this link to live example
- When table is displayed with Chip component within cell
- And user uses NVDA tool to navigate within table
- And user uses arrow keys to hover over table cell with Chip component
- Then NVDA states that Chip is clickable
Current behavior
Chip component is labelled as clickable in NVDA
Expected behavior
Default clickable flag false
Context
NVDA screen reader displays Chip component within table cell to be clickable when it shouldn't
Your environment
npx @mui/envinfo
Chrome 155.0.8059.85
Latest MUI
Search keywords: Chip
Activity
A-Raphie commentedon Oct 20, 2026
Could you paste the rendered outerHTML of the non-clickable Chip from the sandbox (the root element is enough)? In the current
masteraChipwithoutonClick/onDelete/clickableresolvesclickabletoundefinedand renders a plaindivroot - norole="button", notabIndex, and theclickableclass (the one that addscursor: pointer) is not applied. NVDA announces "clickable" from either a button-like role or pointer-cursor styling, so the exact rendered markup + which MUI version/v8-beta the sandbox resolves would pin down where the clickable semantics leak in (app wrapper vs the component).ZeeshanTamboli commentedon Oct 21, 2026
I am not able to reproduce this issue using NVDA. It does not announce with the word "clickable" to me. Which version of NVDA are you using? I am using version
2026.2.0.57664. Maybe you need to upgrade your NVDA version.