Porsche Design SystemSearchNavigate to GitHub repository of Porsche Design SystemOpen sidebar
ConfiguratorExamplesUsageAccessibilityAPI
Checkbox 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 for a list of options when you want the user to select one, none, or multiple options. Use when an explicit action is required to apply to settings. Use the default view for checkboxes when no option is selected. Use the indeterminate state only as a visual state and not as a direct user interaction. Nest when a parent and child relationship is needed. Use short and descriptive label text for each checkbox option. Provide validation messages for each checkbox option if needed. Set vertically left-aligned for better scannability. Don't: Avoid using when you have more than 8 options to choose from or consider using a Select. Don't mix Radio Button buttons with checkboxes. Don't change the selection of another checkbox when a nested one is clicked. The only exception is when a checkbox is used to make a bulk selection of multiple items. Related Components Radio Button Select
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%