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
Input Number Table of Contents Accessibility support Keyboard Key / stateFunctionTab, Shift-TabMoves focus to the next (or previous) focusable element.Arrow Up/DownSets increments/decrements in regards of the steps ARIA enhancements External ARIA provided by the aria property: Use the aria property to pass supported attributes to the native control inside the shadow DOM. Prefer a visible label for the accessible name. Use aria-label when the label is hidden or insufficient, and aria-description for extra context that should not replace the name. ARIAUsagearia-labelDefines an accessible name when the visible label is insufficient or hidden; prefer a visible label for most cases.aria-descriptionProvides additional context for assistive technologies without replacing the accessible name. Internal ARIA that is managed by the component: ARIAUsagearia-describedby="IDREF"Defines the accessible description combined with the status message.role="status", role="alert"When message and state or loading prop change, the status message is announced.aria-hidden="true"If required attribute is set, the visible asterisk indicator is hidden from assistive technologies.aria-invalid="true"If error state is set.aria-live="polite"If the maxlength attribute is present, the counter is announced via ARIA live region. Development considerations Exposing the unit prop The unit prop is not exposed to assistive technologies by default. If you provide a unit abbreviation, you need to dissolve it in real text through the description prop. For example, if you use kmh, you can set the description prop to kilometers per hour. This way, the screen reader will read out the full text. Disabled state In general, avoid using the disabled state. Disabled elements are no longer focusable and may be missed by screen reader users. They can also confuse sighted users if the reason they are disabled is not made clear. Common do's and don'ts Do pass extra labelling through the aria prop (aria-label, aria-description). Do keep a persistent label and spell out unit abbreviations in the description prop. Do use the component state/message API so validation and status changes are announced. Do use clear error wording that helps users recover. Don't rely on placeholder text or the unit prop alone for accessible context. Don't use hide-label without an accessible name. Don't add native aria-* attributes directly on the component host. 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-labelledby🚫aria-describedby🚫 Integration examples
ARIA on component host vs aria prop❌ Anti-pattern
<p-input-number name="quantity" label="Quantity" aria-label="Accessible name" aria-description="Additional context"></p-input-number>
✅ Recommended
<p-input-number name="quantity" label="Quantity" aria="{'aria-label': 'Accessible name', 'aria-description': 'Additional context'}"></p-input-number>
Placeholder used as the only label❌ Anti-pattern
<p-input-number name="speed" placeholder="Top speed" unit="kmh"></p-input-number>
✅ Recommended
<p-input-number name="speed" label="Top speed" unit="kmh" description="Enter the maximum speed in kilometers per hour."></p-input-number>
Hidden label without accessible name❌ Anti-pattern
<p-input-number name="speed" hide-label="true"></p-input-number>
✅ Recommended
<p-input-number name="speed" hide-label="true" label="Top speed"></p-input-number>
Validation feedback via state and message API❌ Anti-pattern
<p-input-number name="speed" label="Top speed" aria-invalid="true" message="Invalid"></p-input-number>
✅ Recommended
<p-input-number name="speed" label="Top speed" unit="kmh" description="Enter the maximum speed in kilometers per hour." state="error" message="Enter a speed between 0 and 350 kilometers per hour."></p-input-number>
Tests Automated TechnologySupportAXE-Core (WCAG 2.2 AA, Best-Practice)✅High-Contrast Mode (light/dark)✅Text-Zoom (200%)✅ Manual TechnologySupportKeyboard✅Screen reader (VoiceOver, NVDA)✅
v4.8.0v2v1
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%