Other Occurrences — Name, Role, Value
When a page is analysed, the same accessibility issue may appear on many elements. Instead of creating a separate report for every instance, the report creates one representative issue and groups the remaining matching elements under Other occurrences.
This keeps the report readable while still showing every affected element.
How grouping works
The grouping behaviour depends on which kind of Name/Role/Value problem was detected.
Missing accessible name
All elements missing an accessible name are grouped together, because they share the same underlying problem: assistive technologies cannot identify them by name.
This grouping does not depend on the type of element or its semantics. Different kinds of control can appear in the same group as long as they all lack an accessible name.
Missing role
Elements missing a role are grouped only when they represent the same interaction pattern or serve the same semantic purpose.
If different patterns are detected — interactive containers versus custom menu items, for example — they are reported as separate groups.
Name and role together
Elements that have both a name and a role are grouped by element type and similar semantics.
Components that behave the same way — custom buttons, or custom links — are grouped together, while different component types generate separate issues.
Main issue versus other occurrences
Each group contains:
- One main issue, which serves as the representative example and carries the complete explanation, the impact, and the recommended fix.
- Other occurrences, listing every additional element with the same kind of problem.
Treat the main issue as the reference for understanding and fixing the rest of the elements in its group.