Why this wireframe works | Tag filters
Articles for the pressed tag appear right away
If results only appear after pressing a button, every choice takes an extra step. Each time a tag is pressed, the list and the count are swapped in place.
Several tags narrow the list with “matches any”
If choosing two tags of the same kind only shows articles that match both, the list quickly drops to zero. Tags of the same kind use “matches any”, which widens the results.
Selected tags are shown with a fill and a check mark
If only color marks the selection, people who find colors hard to tell apart miss it. Selected tags are filled in black and also get a check mark.
On mobile, the tags scroll sideways in one row
Wrapping the tags onto several lines pushes the list down the screen on mobile. On mobile, the tags sit in one row that scrolls sideways.
Common mistakes when building it
Lining up 30 or 40 tags
With too many tags, people tire just reading them before choosing. Narrow them down to the commonly used ones, and if more are needed, consider splitting them by kind of filter.
Reloading the page on every choice
The screen goes blank on every press, and people lose track of where they were. Swap only the list.
No way back to “All”
People can’t work out how to remove tags and leave with the list still filtered. Put “All” first, and let it clear every selection at once.
Not announcing that the count changed
Even when the list visibly changes, screen reader users are not told. Update the count sentence and announce it with aria-live or similar.
Frequently asked questions
Should the URL change when a tag is pressed?
If people should be able to share the filtered list, or return to the same state with the back button, keep the filter in the URL, as in ?tag=SEO. For topics you want in search results, a separate category list page is more reliable than a filter.
When several tags are selected, should results match any of them or all of them?
“Matches any” is the norm for tags of the same kind. With “matches all”, every extra choice cuts the count, and the list easily drops to zero.
Should tags be built as buttons or checkboxes?
Since each press toggles the selection, use a button with aria-pressed, or a checkbox styled as a tag. Either way, make sure screen readers announce whether it is selected.

























