This registry is intended to provide a framework for [[wcag-3.0]] to include text metrics from a wide range of scripts and languages. Including specific text metrics in the main document is prohibitive in terms of how to present multiple languages. Separating the specific metrics for different scripts from the main document allows for scripts to be added independently to the recommendation. Ultimately this supports quicker adoption as more is learned about the needs of readers of different scripts and languages.

The registry is non-normative.

To comment, file an issue in the W3C wcag3 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, email public-agwg-comments@w3.org (comment archive). In-progress updates to the registry can be viewed in the public editors’ draft.

Introduction

TBD

Purpose

TBD

Organization

TBD

Entry requirements

• Each entry must include a unique pairing of script name and applicable language code. The language code must be a valid [[iso-639-2023]] code. If the text metric guidance is broadly applicable to all languages using that script then "All" should be used. More specific script/language pairings will take precedent over a general script/"All" entry.
• Each entry must include a link that references a publicly available normative specification. It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
• Specifications external to W3C should follow the principals outlined in the W3C Technical issues Lead Team guidance to Normative References
• Each referenced specification must include the following sections
  • Blocks of text readable (minimum)
  • Blocks of text readable (enhanced)
  • Text style readable (minimum)
  • Text style readable (enhanced)
  • Blocks of text adjustable
  • Text style adjustable
• Each section must only contain guidance on the specifics of how to present text using the identified script for any specified language.
• Where there are no specific metrics that must be included, a section should still be included with the text "Not applicable".
• Candidate entries must be announced by filing an issue in the WCAG3 GitHub repository
• If the Accessibility Guidelines Working Group reaches consensus to accept the candidate, a pull request should be drafted to register the candidate. The registry editors will review and merge the pull request.
• Entries may be updated to include a reference to a more recent version of the referenced specification.
• Entries may be deleted or deprecated.
• Deleted or deprecated script/language pairings may be reused.

Registry