1 / 5
A component doc that says when to use a banner vs a toast provides ___ guidelines.
-
-
-
-
Usage guidelines tell consumers which component fits which situation, preventing misuse and inconsistency.
2 / 5
Paired examples showing correct and incorrect use are ___.
-
-
-
-
Do's and don'ts make abstract rules concrete by contrasting right and wrong applications side by side.
3 / 5
Labelling the parts of a component (label, icon, container) documents its ___.
-
-
-
-
Component anatomy gives shared vocabulary so designers and engineers refer to the same parts unambiguously.
4 / 5
Noting required ARIA labels and contrast ratios adds ___ guidance.
-
-
-
-
Accessibility notes ensure every consumer of the component meets a11y standards by default rather than rediscovering them.
5 / 5
Documenting available variants and states (default, hover, disabled) describes the component's ___.
-
-
-
-
Listing variants, props, and states defines the component's contract so it's used consistently across the product.