Table with clickable rows accessibility

[Sxoo]

Hi there! Thank you for this excellent library.

I've been testing the Table component with screen readers and discovered an accessibility issue with clickable rows and cells. Currently, screen reader users receive no indication that rows or individual cells are interactive elements that will navigate to other pages when activated.

Specific issues:

• Clickable table rows are announced as regular rows without any indication of interactivity
• Individual clickable cells within rows lack proper semantic meaning for assistive technology
• Users have no way to discover these interactive elements when navigating with a screen reader

Questions:

1. What's the recommended approach for making clickable table rows accessible to screen reader users? I tried adding aria-labels to Rows but it seems not possible.
2. Should clickable cells have additional ARIA attributes or semantic markup?
3. Are there established patterns within react-aria for this use case that I might have missed?

I'd appreciate any guidance on best practices for implementing accessible interactive tables with your components.

[snowystinger]

• Clickable table rows are announced as regular rows without any indication of interactivity

They aren't links because aria doesn't have a row-link combined role at this time. Perhaps the rowheader should provide some additional information there. Might be considered application specific, so I think you were headed in a generally good direction. Maybe try an additional aria-label on something inside the rowHeader cell, or on the cell if it accepts it.

• Individual clickable cells within rows lack proper semantic meaning for assistive technology

This isn't quite supported yet, at least not from Table's point of view, which is why Row Actions are documented, but Cell Actions are not.

• Are there established patterns within react-aria for this use case that I might have missed?

I do not believe so yet, could just be oversight. Or possibly I'm misremembering, we'll see if anyone else chimes in. Otherwise, I'd give the first idea a go.

[devongovett]

Linking more info about role="row" not being allowed to be an <a> element: w3c/html-aria#473