Filters reachable by URL
When the page offers to filter or sort a list, at least one filtered view is reachable by URL - a link carrying a filter query parameter, or a GET form around the controls. Warns when controls are served but no filtered view has its own URL. Fails when the page offers filtering and serves no operable control at all. Skips on pages that offer no filtering.
Adoption of what this check tests is still climbing, so failing it is an opportunity rather than a defect. Remediation lists rank these after established fixes, and the weight moves only when measurement earns it.
No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind operability.filters_addressable is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.
Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.
Make filtered and sorted views addressable: put the facet state in the query string and link to it, or wrap the controls in a `<form method="get">`. An agent can request `?sort=price_asc` on the first try; a script-only widget it has to operate blind is the single largest published cause of agent failure on real sites.
Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.
Scan my site →