DS Component: Numeric Stepper

[namtheho]

Description

Design Specs: https://www.figma.com/design/jFbAR0o364WhsjELfxl2SI/branch/EfD6ayRO4unQCvdPTqxVQC/Playbook-2.0-%2F-Components?node-id=7250-4840&node-type=canvas&t=iT7RH6ejWjcX9QHJ-0

Problem
Anderson, Wesley has created a new component that needs to be available for domain teams to use for their products. The numeric component needs to be available in code for web

Approach / Solution

• Spike on the design specs that is captured in Figma
• Capture any questions or parts of the design spec that needs clarification to ensure technical feasibility + implementation
• Review, align, and/or collaborate  with the Evo DS team on component design specs, documentation, and A11Y.
• Update requirements as needed

Success Criteria

• Numeric stepper meetings design specs & requirements as agreed upon w/ the Evo team
• Numeric stepper has been demo'd to the Evo DS team
• Numeric stepper component passes UAT & A11Y
• Numeric stepper has code documentation for domain engineers
• Numeric stepper is available in Playbook with the correct link to the code repo, engineer documentation, and version number.

Screenshots

No response

Figma link

https://www.figma.com/design/jFbAR0o364WhsjELfxl2SI/branch/EfD6ayRO4unQCvdPTqxVQC/Playbook-2.0-%2F-Components?node-id=7250-4840&node-type=canvas&t=iT7RH6ejWjcX9QHJ-0

Engineering pre-requisites

• Successful design review with Design System Team.
• Supports dark mode.
• Supports responsive design.
• Tokens have been provided (or already exist).
• Successful accessibility review with Core A11Y Team.
• Successful frontend review with eBayUI Team.

[kcarboy]

Blocked due to a11y:

• a11y + eBayui meeting to further iron out any accessibility concerns (ensuring arthur, andrew, ian are present)
• Demo of various focus state behavior https://xj6wq7-5173.csb.app/

Documentation will change, and updates will include:

• whatever comes out of a11y and focus state behavior
• min/max treatments