Porsche Design SystemSearchNavigate to GitHub repository of Porsche Design SystemOpen sidebar
ConfiguratorExamplesUsageAccessibilityAPI
Button Table of Contents Usage The following segment provides instructions for designers and developers regarding the appropriate utilization of this component in various situations. Do: Use buttons for actions that have clear consequences, such as submitting a form or initiating a purchase. Use buttons to indicate the next step in a process, such as "Continue" or "Next". Use buttons with clear and concise labels that accurately describe the action they perform. Use the primary button for the most important or desired action, and use the secondary button for less important or secondary actions. Use icons in buttons to enhance their meaning, but ensure the icon is relevant and easily recognizable. Use disabled buttons to indicate actions that are currently unavailable or incomplete, and provide context for why the button is disabled. Don't: Don't use buttons for non-actionable elements, such as decorative graphics or text. Don't use ambiguous or unclear labels for buttons, as it can lead to confusion for users. Don't use too many buttons on a page or in a single section, as it can overwhelm users and reduce usability. Don't use primary and secondary buttons interchangeably, as it can confuse users and reduce the clarity of your interface. Don't use disabled buttons without providing context for why the button is disabled. This can lead to confusion and frustration for users. Related components Button Group Links
Global settingsThemeChanges the theme of the application and any Porsche Design System component. It's possible to choose between forced theme light and dark. It's also possible to use auto, which applies light or dark theme depending on the operating system settings automatically.LightDarkAuto (sync with operating system)DirectionThe 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%