We currently use patterns to represent two different concepts:
One violation found across multiple pages.
One component with violations, and this component is found across multiple pages.
Some clients I know have been confused by this dual meaning, so I think it could be useful to separate the component concept into its own feature.
It could have one image at the component level that shows the component, so that clients will have a clear idea of what component we're referring to when we log violations against it (no more confusion between a
<select> and a "dropdown menu"). This would also differentiate it further from a pattern, which would only have an image at the violation level.