Key / stateFunctionTab, Shift-TabMoves focus to the next (or previous) focusable element.Arrow Up/DownSets increments/decrements in regards of the steps
ARIA enhancements
Internal ARIA that is managed by the component:
prev
next
ARIAUsagearia-describedby="STRING"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.
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, you should prevent using the disabled state. Disabled elements are not reachable (focusable) anymore and
can be missed by screen reader users. They can be confusing for sighted users as well by not pointing out why these
elements are disabled.
Due to the nature of Web Components and shadowDOM, there are limitations in the usage of some ARIA
attributes if they try to set relationship between elements in different shadowDOM's or shadowDOM/lightDOM combinations.