A table block is a record set laid out in rows and columns so it can be scanned before any of it is read: a sortable header, one leading cell per row that the record is known by, and a single action column at the end. Hovering washes the whole row rather than the cell under the pointer, because the row is what the reader is aiming at, and selection is a checkbox with the count said out loud above the header.
The thing that decides whether a table holds up is the empty cell. A blank and an em dash are two different facts (nobody has filled this in, against this was recorded as none) and a table that draws them identically loses the distinction without telling anyone. Column width is the other one. It belongs to the kind of content in the column, not to the header text, so a status column is the same width in every table you build and a row of them lines up down the page.
A record per company or person, with a mark, the contact to talk to and where the relationship currently stands. Status lives in a badge, so a column of them can be taken in without reading a word of it.
Work in flight: an owner, a deadline and a progress bar carrying its own figure. The avatar group collapses past a few faces, which keeps the column the same width however large the team grows.
Documents with a type mark, an uploader and a sharing switch that applies the moment it is flipped. Delete and share sit together in one column at the end rather than following each value around.
Assets carrying tags and a score. Both are expensive column types: a badge group has to truncate to a count, and a rating is read-only here, since five clickable stars inside a scanning surface invite mis-clicks.
Avoid sideways scrolling. A table cut off at the edge ends mid-column, and nothing on screen says the rest exists. Drop the columns that are present but not what anyone came for first. Below that, turn each row into a card with the column name printed beside every value, and keep the leading cell looking the same the whole way down so rows stay recognisable.
In the header cell, beside the label, sorting that column and nothing else. Mark the sorted header with aria-sort so assistive technology reports the direction, and make the whole header cell the target rather than a small glyph beside it. Not every column earns one: sorting a free-text description achieves nothing, and a header that looks sortable but is not is worse than a plainly inert one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A table block is a record set laid out in rows and columns so it can be scanned before any of it is read: a sortable header, one leading cell per row that the record is known by, and a single action column at the end. Hovering washes the whole row rather than the cell under the pointer, because the row is what the reader is aiming at, and selection is a checkbox with the count said out loud above the header.
The thing that decides whether a table holds up is the empty cell. A blank and an em dash are two different facts (nobody has filled this in, against this was recorded as none) and a table that draws them identically loses the distinction without telling anyone. Column width is the other one. It belongs to the kind of content in the column, not to the header text, so a status column is the same width in every table you build and a row of them lines up down the page.
A record per company or person, with a mark, the contact to talk to and where the relationship currently stands. Status lives in a badge, so a column of them can be taken in without reading a word of it.
Work in flight: an owner, a deadline and a progress bar carrying its own figure. The avatar group collapses past a few faces, which keeps the column the same width however large the team grows.
Documents with a type mark, an uploader and a sharing switch that applies the moment it is flipped. Delete and share sit together in one column at the end rather than following each value around.
Assets carrying tags and a score. Both are expensive column types: a badge group has to truncate to a count, and a rating is read-only here, since five clickable stars inside a scanning surface invite mis-clicks.
Avoid sideways scrolling. A table cut off at the edge ends mid-column, and nothing on screen says the rest exists. Drop the columns that are present but not what anyone came for first. Below that, turn each row into a card with the column name printed beside every value, and keep the leading cell looking the same the whole way down so rows stay recognisable.
In the header cell, beside the label, sorting that column and nothing else. Mark the sorted header with aria-sort so assistive technology reports the direction, and make the whole header cell the target rather than a small glyph beside it. Not every column earns one: sorting a free-text description achieves nothing, and a header that looks sortable but is not is worse than a plainly inert one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
8 companies · 2 pending renewal
8 companies · 2 pending renewal
8 companies in three stages
8 companies · 2 pending renewal
8 companies · 2 pending renewal
8 companies in three stages