Porsche Design System Search Navigate to GitHub repository of Porsche Design System Open sidebar prev nextConfigurator Usage Accessibility API Marque 🚫
Table of Contents
This component is deprecated and will be removed with the next major release. Please use
p-wordmark instead.
Sizes#
Slight adjustments ensure that the Porsche marque is optimally perceived as equally as possible in the various image
sizes.
prev next
Size UsageSmall Viewports with 1299 px width or lowerMedium Viewports with 1300 pixel width or larger
Content#
The two elements that make up the overall logo for the Porsche marque are the word "Porsche" (logotype) and the
Porsche Crest as an image-based logo. The three-dimensional colored Porsche marque is used as a fixed unit, always
including crest and logotype, across all media, and may not be changed .
Usage#
Within static digital applications, the Porsche Marque is always used without shadow . For moving images a separate
Crest with shadow is available.
The Porsche Marque may only be used on a white background .
Do's & Don'ts#
The marque may not be altered in relation to its two elements or their size. The marque may never be used without
the Porsche lettering, as the sender identification cannot be guaranteed.
The Porsche marque may not be used against coloured or busy backgrounds (e.g. shading). As the Porsche crest has a
high level of graphical complexity, excessive visual turmoil may be created.
Global settingsTheme
ThemeMore information Changes 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. // TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
Light// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
Dark// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
Auto (sync with operating system)DirectionMore information Changes the direction of HTML elements, mostly used on<html>
tag to support languages which are read from right to left like e.g. Arabic. // TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
LTR (left-to-right)// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
RTL (right-to-left)// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
AutoText ZoomMore information Changes the text size and values with unit rem
or em
relatively. This setting can be defined in browser settings for any website or by an application itself on<html>
tag. To achieve WCAG 2.2 AA compliance it's obligatory to support text zoom up to at least 200%. // TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
100%// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
130%// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
150%// TODO: get rid of ARIA sprouting and use `elementInternals` API when AXE-CORE supports it: https://github.com/dequelabs/axe-core/issues/4259
200%