Want to revisit/expand upon our design guidelines (and possibly update our demos as a result) around clickable table rows with other nested interactions in our primary detail pattern. Our current primary/detail demos may not be very accessible.
This topic was brought up by Asumi/HCC team during the UXD PF design share today (11/11). Some of the open questions we discussed:
What is the desired/most accessible interaction for clickable table rows with nested clickable elements within them?
Should clicking anywhere on the whole row open the details panel, or should we follow something similar to clickable cards where clicking the title of the row opens detail drawer?
James also said that his product is requesting that the clicking anywhere on the row actually selects it for bulk actions/checkbox select.
Eric on Accessibility:
It could potentially be an issue to have a clickable item on top of another clickable item. Could cause a misclick when attempting to click smaller action within larger action. Alternative: have a separate button within the table row or card specifically for triggering a drawer to open. see: https://www.tempertemper.net/blog/overlapping-interactive-areas
Want to revisit/expand upon our design guidelines (and possibly update our demos as a result) around clickable table rows with other nested interactions in our primary detail pattern. Our current primary/detail demos may not be very accessible.
This topic was brought up by Asumi/HCC team during the UXD PF design share today (11/11). Some of the open questions we discussed:
Eric on Accessibility: It could potentially be an issue to have a clickable item on top of another clickable item. Could cause a misclick when attempting to click smaller action within larger action. Alternative: have a separate button within the table row or card specifically for triggering a drawer to open. see: https://www.tempertemper.net/blog/overlapping-interactive-areas
FYI @kaylachumley @bekah-stephens @asumihasan