You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if we add any buttons or interactions using a custom node, then the accessibility compliance is hit. I checked with couple of my colleagues, and having a pressed state, might help.
When a node is selected it can probably be marked as aria-pressed="true" then the controls inside become interactive or else one other solution could be is to allow custom nodes to fully take over the a11y requirements. That means, not marking the node as button and letting the control inside handle accessibility. This is not possible today as selection is done via the role="button" div which is rendered and managed by React flow.
Any guidance or support will be appreciated
The text was updated successfully, but these errors were encountered:
Please describe the feature that you want to propose
Based on Accessibility guidelines, buttons should not have interactive controls in it. https://dequeuniversity.com/rules/axe/4.5/nested-interactive
So, if we add any buttons or interactions using a custom node, then the accessibility compliance is hit. I checked with couple of my colleagues, and having a pressed state, might help.
When a node is selected it can probably be marked as aria-pressed="true" then the controls inside become interactive or else one other solution could be is to allow custom nodes to fully take over the a11y requirements. That means, not marking the node as button and letting the control inside handle accessibility. This is not possible today as selection is done via the role="button" div which is rendered and managed by React flow.
Any guidance or support will be appreciated
The text was updated successfully, but these errors were encountered: