Skip to content
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

Closed
geospatialem opened this issue Mar 22, 2023 · 5 comments
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. a11y Issues related to Accessibility fixes or improvements. Calcite (dev) Issues logged by Calcite developers. enhancement Issues tied to a new feature or request. estimate - 5 A few days of work, definitely requires updates to tests. i18n-l10n issues dealing with internationalization/localization impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality

Comments

@geospatialem
Copy link
Member

Description

Provide context to assistive technology (AT) users when the textarea component's character count is exceeded, something like:

Maximum character length is ${maxLength}, current length is ${currentLength}

The above will require support for a wide audience, including:

  1. AT support, and
  2. Translation support
    • The maxLength and currentLength 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

  1. Provide context to assistive technologies (e.g., JAWS, NVDA, VoiceOver) when textarea's character count is exceeded
  2. Include translation strings, which provide proper grammatical context across our supported locales

Relevant Info

Pertains to the new component, textarea from PR #5644

Which 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)

@geospatialem geospatialem added enhancement Issues tied to a new feature or request. a11y Issues related to Accessibility fixes or improvements. p - high Issue should be addressed in the current milestone, impacts component or core functionality 1 - assigned Issues that are assigned to a sprint and a team member. i18n-l10n issues dealing with internationalization/localization estimate - 5 A few days of work, definitely requires updates to tests. labels Mar 22, 2023
@github-actions github-actions bot added Calcite (dev) Issues logged by Calcite developers. impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone labels Mar 22, 2023
@geospatialem
Copy link
Member Author

Reallocating to the May release, work will be conducted after the nav component work.

@anveshmekala anveshmekala added 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels May 24, 2023
anveshmekala added a commit that referenced this issue May 25, 2023
…t exceeds. (#7021)

**Related Issue:** #6630

## Summary

This PR will add message string in `calcite-text-area` to improve
context of error message when character limit exceeds.
anveshmekala added a commit that referenced this issue Jul 10, 2023
…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.`
@anveshmekala anveshmekala added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Jul 10, 2023
@github-actions
Copy link
Contributor

Installed and assigned for verification.

@geospatialem
Copy link
Member Author

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.

@geospatialem geospatialem added 2 - in development Issues that are actively being worked on. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Jul 24, 2023
@geospatialem geospatialem removed their assignment Jul 24, 2023
@anveshmekala anveshmekala added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 2 - in development Issues that are actively being worked on. labels Jul 28, 2023
@anveshmekala anveshmekala added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Aug 2, 2023
@github-actions github-actions bot assigned geospatialem and unassigned anveshmekala Aug 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2023

Installed and assigned for verification.

anveshmekala added a commit that referenced this issue Aug 2, 2023
…er limit exceeds (#7412)

**Related Issue:** #6630

## Summary
This PR will provide additional context for Assistive Technology users
when character limit exceeds. After this change, AT users will receive
error message as soon as the character limit is exceeded.
@geospatialem geospatialem added 4 - verified Issues that have been released and confirmed resolved. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Aug 2, 2023
@geospatialem
Copy link
Member Author

Verified in 1.5.0-next.33 with JAWS in Chrome and NVDA in Firefox.

benelan pushed a commit that referenced this issue Aug 3, 2023
…er limit exceeds (#7412)

**Related Issue:** #6630

## Summary
This PR will provide additional context for Assistive Technology users
when character limit exceeds. After this change, AT users will receive
error message as soon as the character limit is exceeded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. a11y Issues related to Accessibility fixes or improvements. Calcite (dev) Issues logged by Calcite developers. enhancement Issues tied to a new feature or request. estimate - 5 A few days of work, definitely requires updates to tests. i18n-l10n issues dealing with internationalization/localization impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality
Projects
None yet
Development

No branches or pull requests

2 participants