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

name and short_name (and other localizable member's) relationship to localization and accessibility #1085

Closed
aphillips opened this issue May 15, 2023 · 1 comment · Fixed by #1101
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link
Contributor

name member
https://w3c.github.io/manifest/#name-member

The manifest's name member is a string that represents the name of the web application as it is usually displayed to the user (e.g., amongst a list of other applications, or as a label for an icon).

The name member serves as the accessible name of an installed web application.

The "accessible name" and the display name (or its short_name equivalent) really should be localized to match the expectation of the user. Many apps are localized into many languages, but the design of manifest (with lang and dir as top level items applying to all values inside the manifest and an on-going discussion about localization) suggests that this is not yet fully baked.

@aphillips aphillips added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label May 15, 2023
@aphillips aphillips changed the title name and short_name relationship to localization and accessibility name and short_name (and other localizable member's) relationship to localization and accessibility May 15, 2023
@christianliebel
Copy link
Member

#1101 hopefully addresses this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants