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

A11y labels on increment/decrement buttons of numeric are not localized #617

Closed
m-akinc opened this issue Jun 23, 2022 · 3 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@m-akinc
Copy link
Contributor

m-akinc commented Jun 23, 2022

🐛 Bug Report

In some cases, we use icon buttons (i.e. buttons with content-hidden) within other components, like the number field (for the inc/dec buttons). In those cases, we still provide a hidden label string for the sake of accessibility. Those strings are not getting localized.

💻 Repro or Code Sample

N/A

🤔 Expected Behavior

Even hidden labels should be localized.

😯 Current Behavior

Hidden labels are not localized.

💁 Possible Solution

N/A

🔦 Context

We want screen readers to work well with our components on non-English systems.

🌍 Your Environment

N/A

@m-akinc m-akinc added bug Something isn't working triage New issue that needs to be reviewed labels Jun 23, 2022
@m-akinc m-akinc removed the triage New issue that needs to be reviewed label Jun 28, 2022
@m-akinc m-akinc changed the title A11y labels on icon buttons are not localized A11y labels on increment/decrement buttons of numeric are not localized Jun 28, 2022
@nate-ni nate-ni moved this from Backlog to Defined/Ready to Pickup in Nimble Design System Priorities Jan 3, 2023
@atmgrifter00
Copy link
Contributor

@rajsite or @jattasNI, what is our strategy for dealing with these kinds of localization problems? It would be helpful when someone looks at this issue that there is some documented strategy (even if it's "we have no strategy to address this") in place in the comments so we know we can either ignore it, or know what the problem space is for the issue (i.e. "solve localization at large for Nimble").

@jattasNI
Copy link
Contributor

jattasNI commented Feb 6, 2023

Our strategy so far has been to expose an API that allows clients to provide all the user-facing strings that the component needs. We can provide default English values for those strings but document that apps should provide their own localized values for them.

I don't see us trying to add localization infrastructure for Nimble itself any time soon.

If whoever picks this up can think of a CONTRIBUTING doc to document this policy, feel free to add a note as part of the fix for this.

@mollykreis mollykreis self-assigned this Feb 13, 2023
@mollykreis mollykreis removed their assignment Apr 14, 2023
@m-akinc m-akinc moved this from Defined/Ready to Pickup to Done in Nimble Design System Priorities Sep 18, 2023
@m-akinc
Copy link
Contributor Author

m-akinc commented Sep 18, 2023

Fixed by #1328

@rajsite rajsite closed this as completed Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

6 participants