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

Internationalisation updates (normative) #4263

Open
alastc opened this issue Mar 5, 2025 · 2 comments
Open

Internationalisation updates (normative) #4263

alastc opened this issue Mar 5, 2025 · 2 comments
Labels
i18n i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. Normative

Comments

@alastc
Copy link
Contributor

alastc commented Mar 5, 2025

There is an issue about how some WCAG 2.0/2.1 criteria apply across languages/scripts.

There is a long-ish list on the i18n repo, and a recent issue for a reasonable overview.

This issue is to provide a place to track potential normative updates to WCAG 2.2. These would be class 3 updates, so will need to go through full process. (And then we'd have to work out how to publish in terms of versioning etc.)

As an example, murata2makoto suggested:


Here is my proposed rewrite of 1.4.12 Text Spacing.

Line height (line spacing) to at least 1.5 times the font size;

Replace this bullet by "Sufficient line height (line spacing) in proportion to the font size" or specify that this particular condition applies to English and the like only.

Spacing following paragraphs to at least 2 times the font size;

Replace this bullet by "Sufficient spacing after paragraphs in proportion to the font size" or specify that this particular condition applies to English and the like only.

Letter spacing (tracking) to at least 0.12 times the font size;

Replace this bullet by "Sufficient letter spacing (tracking) in proportion to the font size" or specify that this particular condition applies to English and the like only.

Word spacing to at least 0.16 times the font size.

Replace this phrase by "Sufficient word spacing in proportion to the font size" or specify that this particular condition applies to English and the like only.


There are other suggestions in the recent issue, and many more in the long-ish list on the i18n repo.

We need to work through issues such as:

  • Can we use a word like "sufficient" in normative text, and link to various other standards in informative documents.
  • Can we just except non-latin languages?

I anticipate multiple PRs on this topic, but this issue is to track these potential updates. We should also use this work to close off some previous issues in this repo.

@xfq xfq added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Mar 6, 2025
@yatil
Copy link
Contributor

yatil commented Mar 6, 2025

This would make something that is easily pass/failable in the languages where it applies (I can speak for English and German, where these are sensible sizing options for disabled people) and make it basically untestable (what is “sufficient” in which language?)

@murata2makoto
Copy link

If the goal is to completely avoid the risk of an unfair recommendation, one approach would be to create a separate specification that applies only to Western languages. This would ensure that the guidance remains meaningful within the linguistic contexts where it is relevant.

On the other hand, if maintaining compatibility with the current WCAG text is a priority, then all provisions that only apply to Western language text should be explicitly marked as such. This would provide clarity on the scope of applicability and prevent misinterpretation in languages where these provisions do not hold.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. Normative
Projects
None yet
Development

No branches or pull requests

4 participants