separator

Visual and semantic content separator

Use a native hr for a horizontal separator. Add aria-orientation="vertical" only when it is presented as a vertical divider.

<hr />
<hr aria-orientation="vertical" />

Example

View source
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <title>AngularCSS Separator</title>
    <link rel="stylesheet" href="../../css/preflight.css" />
    <link rel="stylesheet" href="../../css/angular.css" />
    <link rel="stylesheet" href="../example.css" />
    <script src="../../js/angular-ts.umd.js"></script>
    <script src="../../js/angular-css.umd.js"></script>
  </head>
  <body ng-app="angular.css" ng-cloak data-example="separator-demo">
    <main class="visual-example">
      <section data-example="separator-demo" class="separator-copy-demo">
        <div>
          <strong>AngularCSS</strong>
          <p class="muted">HTML-first styles for enterprise applications</p>
        </div>
        <hr />
        <p>
          A set of beautifully designed components that you can customize,
          extend, and build on.
        </p>
      </section>

      <section data-example="separator-list" class="separator-list-demo">
        <dl>
          <dt>Item 1</dt>
          <dd>Value 1</dd>
        </dl>
        <hr />
        <dl>
          <dt>Item 2</dt>
          <dd>Value 2</dd>
        </dl>
        <hr />
        <dl>
          <dt>Item 3</dt>
          <dd>Value 3</dd>
        </dl>
      </section>

      <section data-example="separator-menu" class="separator-menu-demo">
        <div><strong>Settings</strong><span>Manage preferences</span></div>
        <hr aria-orientation="vertical" />
        <div><strong>Account</strong><span>Profile &amp; security</span></div>
        <hr aria-orientation="vertical" />
        <div><strong>Help</strong><span>Support &amp; docs</span></div>
      </section>

      <nav
        data-example="separator-vertical"
        class="separator-nav-demo"
        aria-label="Resource links"
      >
        <a href="#blog">Blog</a>
        <hr aria-orientation="vertical" />
        <a href="#docs">Docs</a>
        <hr aria-orientation="vertical" />
        <a href="#source">Source</a>
      </nav>

      <section
        data-example="separator-rtl"
        class="separator-copy-demo"
        dir="rtl"
        lang="ar"
      >
        <div>
          <strong>AngularCSS</strong>
          <p class="muted">الأساس لنظام التصميم الخاص بك</p>
        </div>
        <hr />
        <p>
          مجموعة من المكونات المصممة بشكل جميل يمكنك تخصيصها وتوسيعها والبناء
          عليها.
        </p>
      </section>
    </main>
  </body>
</html>

Installation

Load the AngularCSS stylesheet. This entry needs no AngularCSS JavaScript or angular.css module dependency. Add AngularTS when using application bindings such as ng-model or ng-click. See Installation for the complete setup.

This entry uses native HTML and CSS. AngularCSS registers no runtime directive for it. Native horizontal-rule semantics.

Anatomy

Root styling selector

  • hr

Semantic structure

Use semantic HTML with the root styling selector above. Native elements provide the structure; the stylesheet supplies presentation.

API

Attributes and state

AttributeAccessPurpose
aria-orientationAuthoredSeparator axis: vertical; omit for the native horizontal separator.

Attributes remain authored HTML, native state, or AngularTS inputs. AngularCSS does not write element state.

CSS custom properties

This styling hook does not define component-specific CSS custom properties.

DOM events

This component does not emit a component-specific custom event.

Native DOM events continue to work normally. AngularTS event directives such as ng-click and ng-keydown, plus the data-change model callback, remain application-owned.

Behavior

Native horizontal-rule semantics. AngularCSS supplies styling without a runtime directive. Native HTML owns platform behavior; AngularTS owns application values, commands, and authored state.

AngularCSS does not replace AngularTS interpolation, bindings, structural directives, form controllers, validation, or application state.

Accessibility

Prefer semantic landmarks and native elements inside the layout. Any interactive handles or triggers must retain an accessible name and visible focus indicator.

Authored accessible names and relationships are preserved. Test the final composition with keyboard navigation and assistive technology because labels and content come from the application.

Customization

Target semantic elements, native state selectors, and component classes with ordinary CSS. Behavior and accessible state remain with native HTML and AngularTS; visual choices belong in the application stylesheet.

Read Customization for layer order, design tokens, state variants, and iframe demo isolation.