Skip to contentPorsche Design System
You are currently viewing an earlier release of the Porsche Design System.Switch to the latest Porsche Design System documentation.
SearchGitHub repository of Porsche Design SystemOpen settings sidebar
Tabs Table of Contents Accessibility support Keyboard Key / stateFunctionTab- Moves focus to the active tab.
- When the tab list contains the focus, moves focus to the next element in the tab sequence, which is the tabpanel element.Right Arrow, Left Arrow- Moves focus to the next tab.
- Activates the newly focused tab.
- If focus is on the last tab, moves focus to the first tab.Home, End- Moves focus to the first/last tab and activates it. ARIA enhancements External ARIA provided by the aria property: ARIAUsagearia-label="STRING"Defines a string value that labels the tablist.aria-description="STRING"Defines a string value that adds a more detailed description of the tablist. Internal ARIA that is managed by the component: ARIAUsagerole="tablist"Indicates that the element serves as a container for a set of tabs.role="tab"Indicates the button serves as a tab control.role="tabpanel"Indicates the tabs-item serves as a container for tabpanel content.aria-label="STRING"Adds accessible name to the tabs-item based on the label property.aria-selected="BOOLEAN"Indicates whether the tab is selected and whether its associated tabpanel is visible. Development considerations Labelling When multiple tab groups appear on the same page, or when the purpose of the tabs is not clear from the visible tab labels alone, provide a descriptive accessible name for the tablist using the aria property, e.g.: <p-tabs aria="{ 'aria-label': 'Some label for the tablist', 'aria-description': 'Some description for the tablist' }">. Common do's and don'ts Do pass tablist ARIA through the aria prop when multiple tab groups appear on one page. Do use specific label text on each p-tabs-item. Don't add native aria-* attributes directly on the component host. Don't use vague tab labels like "Details" without context. Limitations Due to the nature of Web Components and shadow DOM, there are limitations when using some ARIA attributes to define relationships between elements across different shadow DOMs or shadow DOM/light DOM combinations. ARIASupportaria-controls🚫 Integration examples
ARIA on component host vs aria prop❌ Anti-pattern
<p-tabs aria-label="Product details">
  <p-tabs-item label="Overview">
    ...
  </p-tabs-item>
</p-tabs>
✅ Recommended
<p-tabs aria="{'aria-label': 'Porsche 911 configuration details'}">
  <p-tabs-item label="Overview">
    ...
  </p-tabs-item>
  <p-tabs-item label="Equipment">
    ...
  </p-tabs-item>
</p-tabs>
Vague tab labels without context❌ Anti-pattern
<p-tabs aria="{'aria-label': 'Product details'}">
  <p-tabs-item label="Details">
    ...
  </p-tabs-item>
  <p-tabs-item label="More">
    ...
  </p-tabs-item>
</p-tabs>
✅ Recommended
<p-tabs aria="{'aria-label': 'Porsche 911 configuration details'}">
  <p-tabs-item label="Overview">
    ...
  </p-tabs-item>
  <p-tabs-item label="Equipment and packages">
    ...
  </p-tabs-item>
</p-tabs>
Tests Automated TechnologySupportAXE-Core (WCAG 2.2 AA, Best-Practice)✅High-Contrast Mode (light/dark)✅Text-Zoom (200%)✅ Manual TechnologySupportKeyboard✅Screen reader (VoiceOver, NVDA)✅
Global settingsColor SchemeAll color tokens use the light-dark() CSS function. Set the theme via the CSS color-scheme property: light for light mode, dark for dark mode, or light dark to follow the user's system preference.LightDarkLight DarkDirectionThe dir global attribute in HTML changes the direction of text and other content within an element. It's most often used on the <html> tag to set the entire page's direction, which is crucial for supporting languages that are written from right to left (RTL), such as Arabic and Hebrew. For example, using <html dir="rtl"> makes the entire page display from right to left, adjusting the layout and text flow accordingly.LTR (left-to-right)RTL (right-to-left)Text ZoomTo ensure accessibility and comply with WCAG 2.2 AA standards, it is mandatory for web content to support text resizing up to at least 200% without loss of content or functionality. Using relative units like rem is a best practice for achieving this, as they allow the text to scale uniformly based on the user's browser settings.100%130%150%200%