Porsche Design System Search Navigate to GitHub repository of Porsche Design System Open sidebar prev nextConfigurator Examples Usage Accessibility API Input Email
Table of Contents
Usage#
The following segment provides instructions for designers and developers regarding the appropriate utilization of this
component in various situations.
p-input-email
is specifically designed for collecting email addresses. It leverages built-in browser validation to
ensure that input follows the correct email format. This makes it a better choice than a generic text input when email
validation, proper keyboard behavior on mobile, and accessibility are important. For further guidance, see the
MDN documentation on email inputs .
Do:
Use when requesting an email address from the user.
Use without a label only when the context is clear.
Use for validation and error of input.
Use asterisk for required fields.
Don't:
Don't use labels with more than two words whenever possible (keep it short and descriptive).
Don't use an instructional or description text for the label.
Related Components#
Text Field Wrapper
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 The 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. // 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)Text ZoomMore information To 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. // 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%