As with all tables, proper markup will help considerably in how the data within them are read. Consider your markup and make sure it's semantic and valid. Avoid using nested tables.
Forms (radio buttons and checkboxes)
Despite our results being in a table, proper use of
id's should be used. In our examples, we're putting the primary piece of result data (i.e., a name or a document number) as the
label for the radio button or checkbox. The row itself should be
aria-labeledby the same
id to tie everything together.
Popovers here should adhere to the same accessibility considerations found for popovers in the Help and Messaging specification document. The use of ARIA should be used along with an indication that the popover is open or closed. Additionally, focus should be sent to the popover content once it's displayed. Closing the popover should return focus back to the initiating element.
As always, use valid, semantic, proper HTML markup to optimize accessibility and usability tables and results list.
W3 HTML Validator