-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TextArea] Provide context to assistive technologies when character count is exceeded #6630
Comments
Reallocating to the May release, work will be conducted after the nav component work. |
…er limit exceeds (#7299) **Related Issue:** #6630 ## Summary This PR will provide additional context for Assistive Technology users when character limit exceeds. After this change, an example error message looks like below: `The current character length is 14, which exceeds the maximum character length of 10.`
Installed and assigned for verification. |
Current context is provided on form submission 👍🏻. Additional efforts will be sought for context as the user is interacting with the component directly, moving back to development to finalize the effort. |
Installed and assigned for verification. |
Verified in |
Description
Provide context to assistive technology (AT) users when the
textarea
component's character count is exceeded, something like:The above will require support for a wide audience, including:
maxLength
andcurrentLength
variables will need to be replaced before reading back to users to ensure wording is translated in a grammatically acceptable manner across locales.Acceptance Criteria
textarea
's character count is exceededRelevant Info
Pertains to the new component,
textarea
from PR #5644Which Component
textarea
Example Use Case
https://codepen.io/geospatialem/pen/GRXwJKy
The solution could consider a
.sr-only
, which is not displayed visually on the page, but provides context to assistive technologies (AT).Priority impact
p1 - need for current milestone
Esri team
Calcite (dev)
The text was updated successfully, but these errors were encountered: