Meaning improves more than accessibility
Browsers provide useful keyboard and form behavior for native elements. Search engines can understand page regions, and developers can read the markup without decoding generic containers.
Use generic containers only when needed
A div or span is appropriate when no meaningful HTML element fits. The goal is not to replace every container, but to choose a native role whenever the content or interaction already has one.
A familiar example
Building site navigation
- A nav element identifies the group as navigation.
- Links take visitors to real destinations.
- The current link uses text or state that remains understandable without color alone.
What to remember
- Choose elements by purpose, not visual shape.
- Native elements bring useful behavior with them.
- Generic containers are tools, not the default answer for every role.