Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

TBL-006 Published

Sortable table

A list table design where pressing a column header sorts the rows by that column.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Sortable table

Sortable table UI design (desktop wireframe)

Wireframe (mobile) | Sortable table

Sortable table UI design (mobile wireframe)

What changes on mobile

  1. Columns kept: Removing columns removes sort axes, so the columns stay and the table scrolls sideways.
  2. A hint about sideways scrolling: People can tell that sortable columns lie beyond the screen.
  3. Header buttons keep their height: Tall enough to press with a thumb.

Before you choose this pattern | Sortable table

Good fit

  • Many rows, and different readers want different orders
  • Lists of documents, properties, projects or jobs where people sort by date, number or name
  • Ten rows or more

Poor fit

  • Few rows that can be seen whole without sorting
  • Narrowing rows by condition (combine with a separate filtering component)
  • The order itself carries meaning (steps, rankings)

Why this wireframe works | Sortable table

Readers sort into the order they want

Some people look for the newest document; others want to start with the shortest. Pressing a column header sorts by that column.

The whole header is clearly pressable

When only the header text is pressable, people do not notice it can be pressed. A button spans the full header width, and the arrow shows it sorts.

The current order is conveyed three ways

An arrow alone can be read as ascending or descending by mistake. Besides the header arrow and background, aria-sort and the caption text state the current order.

Each sort is announced

Rows changing order is invisible to screen reader users. After sorting, “Sorted by pages, most first” is announced.

Numbers and dates sort correctly

Left-aligned numbers or inconsistent date formats sort wrongly and compare poorly. Numeric columns are right-aligned, dates use one format, and a sort value is kept separately.

Common mistakes | Sortable table

Only the header text is pressable

Small pressable text goes unnoticed and is hard to hit. Make the full header width a button and show the arrow.

Inconsistent date formats that sort wrongly

Mixing “September 2026” and “9/10” breaks the order when sorted as text. Use one format and keep a separate sort value.

Reloading the page on every sort

A reload that scrolls back to the top makes readers find the table again. Sort within the page and keep the position.

The order shown by arrow alone

An arrow alone can be misread and does not reach screen readers. Show it with aria-sort and words as well.

FAQ | Sortable table

What should the initial order be?

The order readers use most. For documents and news, newest first is common. State the initial order in the caption.

Are both sorting and filtering needed?

With many rows and readers searching by condition, filtering helps. With up to a few dozen rows that can be found by changing the order, sorting alone may be enough.

Should many rows be split into pages?

Splitting makes it unclear whether sorting applies to the current page or all rows. If you split, sort across all rows and say so.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published