Group by component

A findings list ordered by rule tells you what is wrong. Ordered by component, it tells you what to change.

The findings list grouped by component rather than by rule, so repeated failures collapse into the one element they all come from.

One fix, not fifty

Findings can be grouped by the component they came from rather than by the rule they broke. A list of eighty contrast failures collapses into one entry: a button, used eighty times, with one colour to change.

The grouping is derived from the markup โ€” class names, framework component boundaries, repeated structures โ€” and it shows the evidence it used, so you can see why two things were treated as the same component.

Across pages, too

Run a whole-site scan and the same grouping applies across every page in it. A rule that fails on every page scanned is almost always one shared component.

Start with the page you are on

Install the extension, press F12 and open the Accessibility tab. No account, nothing to configure, and nothing leaves your machine.