Table > Pair with engineering on building an accessible table from the ground up
Context
This issue is created from this comment: &7635 (comment 857753616) in the Table Accessibility audit.
@tauriedavis and @leipert as I'd mentioned in Slack, I'm wondering if we could reverse the approach here where instead of pointing out everything wrong (and not even having full examples to test), we work on building accessible tables from the ground up. It could be much easier and effective to start with requirements and a list of necessary features. There are plenty of great examples to start from, for example, Web Experience Toolkit Tables and https://codepen.io/aardrian/pen/YEKmxP.
In this case we'd deprecate the existing tables and migrate with the new ones. I don't foresee doing this for every component, but for ones without simple fixes, or ones where basic examples don't exist it could save time and be a more constructive experience.
Proposal
Find time to sync with engineering on what it would take to build out an accessible table and schedule that into the next release.
Resources
https://www.smashingmagazine.com/2022/12/accessible-front-end-patterns-responsive-tables-part1/