From 3b8d82346103cbdf64e9195c35523d7c478b7404 Mon Sep 17 00:00:00 2001 From: melloware Date: Fri, 10 Nov 2023 09:30:00 -0500 Subject: [PATCH] Fix #5270: Inputnumber clarity on id vs inputId. --- components/doc/inputnumber/accessibilitydoc.js | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/components/doc/inputnumber/accessibilitydoc.js b/components/doc/inputnumber/accessibilitydoc.js index 435f20ddd5..eb01b1f261 100644 --- a/components/doc/inputnumber/accessibilitydoc.js +++ b/components/doc/inputnumber/accessibilitydoc.js @@ -5,8 +5,8 @@ import { DocSectionText } from '../common/docsectiontext'; export function AccessibilityDoc() { const code = { basic: ` - - + + Number @@ -21,7 +21,8 @@ export function AccessibilityDoc() {

Screen Reader

Value to describe the component can either be provided via label tag combined with inputId prop or using aria-labelledby, aria-label props. The input element uses spinbutton role in addition to - the aria-valuemin, aria-valuemax and aria-valuenow attributes. + the aria-valuemin, aria-valuemax and aria-valuenow attributes. Make sure to assign unique identifiers for the span + and input