Separator
A separator is a visible line that can also mark a real break between parts. If people can focus and move it, it becomes an adjustable splitter.
Another example
A mail app uses a separator that cannot receive focus between command groups. A different separator divides the message list and preview. That separator can receive focus and tells software its direction and position. Arrow keys move it within set width limits.
Main parts
- 01Boundary
- 02Orientation
- 03Optional adjustable value
Use it when
Use a semantic separator only when the break helps explain the structure. Add values and keyboard control only when it is adjustable.
Do not use it when
Do not mark every decorative line as a separator. Do not let a fixed divider receive focus.
Name used in code
hr or role=separator; tabindex and aria-valuenow only when adjustable Before you ship
Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery.
Outcome: Use Separator to solve this user need without losing the current context. User context: A mail app uses a separator that cannot receive focus between command groups. A different separator divides the message list and preview. That separator can receive focus and tells software its direction and position. Arrow keys move it within set width limits. Recommended pattern: Separator. Why it fits: Use a semantic separator only when the break helps explain the structure. Add values and keyboard control only when it is adjustable. Do not use it when: Do not mark every decorative line as a separator. Do not let a fixed divider receive focus. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Separator. Definition: A separator is a visible line that can also mark a real break between parts. If people can focus and move it, it becomes an adjustable splitter. Release checks: Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.