Skip to content

Files

Latest commit

 

History

History
90 lines (69 loc) · 3.89 KB

File metadata and controls

90 lines (69 loc) · 3.89 KB

W3C Logo

Localizations of the Accessibility Metadata Display Guide for Digital Publications

This repository hosts the localizations of the compact and descriptive display statements defined in the Accessibility Metadata Display Guide for Digital Publications.

A localisation visualizer allow human browsing of the different translation packages. A dropdown menu allows to choose the localisation to be displayed.

Contributing to the Repository

Use the standard fork, branch, and pull request workflow to propose changes to the specification. Please make branch names informative—by including the issue or bug number for example.

Editorial changes that improve the readability of the spec or correct spelling or grammatical mistakes are welcome.

Please read CONTRIBUTING.md, about licensing contributions.

Because persons and organizations with different levels of technicality must be able to contribute, we accept both raw files via Pull requests or proposals submitted through email.

Why are there different translations?

An ebook can be purchased in any country without limited availability or additional delivery costs. Readers want consistent display of accessibility information, and that’s the primary role of the display guide.

The wording proposed in this guide has been widely discussed by a large group representing different actors of the English-speaking geographies. It has been improved after proof-of-concept implementations and reviewed by panels of testers.

Different countries or different target audience services may want to use specific language, and we have provided flexibility in the guide to accommodate this while maintaining a high level of understanding and similar quality to help users in a country find comparable information between two bookstores or libraries in the same language area.

Simply translating the strings is not enough; the subtle meaning of the words and phrases of accessibility concepts must be localized for maximum understanding. Therefore, we intend to provide a mechanism for the publishing community to provide translations that localizes the strings for equally effective communication in many languages.

With the rapidly evolving landscape of accessible ebooks available, most concerned persons are discovering a new world. To ensure the information is widely spread and understood, the implementation by local actors like libraries serving persons with disabilities and other local actors in the fight to end the book famine for readers with print disabilities is crucial and should be highlighted.

The localization of the display guide is a good opportunity to make known the rich accessibility features offered by modern formats like EPUB. In addition, having a local project scale to write an understandable vocabulary to describe such features is a precious qualitative approach that will benefit every player in the value chain.

How to choose between localization files?

The first keys of each JSON files contains descriptive information, including:

  • Author, name of the organisation responsible for the establishment and maintenance of this localization
  • Language, a 4-letter identifier where the first two letters specify the language according to ISO 639-1, and the last two letters define a region or script as per ISO 3166-1 alpha-2.
  • Variant, a one word free name to identify your work
  • Audience describes the public. We recommend to use any vocabulary from the ONIX list 28. More than one audience can be informed with a comma separating each.
  • Description, a free field including a short description of how this localization was obtained