When should designers use a table vs. a list for organizing data and information?

[GnatalieH]

Tables are sometimes used on va.gov when a list might be better suited as a solution for organizing data/info. This discussion should gather perspectives from:

• Design
• Accessibility
• Content/IA
• Dev

[GnatalieH]

A11y considerations:

• If the content can be designed as a description list (e.g. 2 column definition and description), it should use a description list.
• If data/info comparison is the goal for using a table, alternative content strategies should be considered first. e.g. Can we anticipate what the user will want to compare or simplify in the comparison process through a step by step flow?
• One column lists will generally be more accessible on mobile screens since they won't (a) require a horizontal scroll or (b) create narrow, unreadable columns.
• The important thing to know about tables from an accessibility perspective is they need to have proper headers.
• Also, the more straightforward the better. Tables nested within tables and tables whose individual rows and columns are of different lengths need to be avoided.
• Tables should really only be used when there’s a logical relationship between the elements of data, and there’s more than two. For example, a bank statement with the date of transaction, amount of transaction, and who the transaction is with makes sense to be in table form.