- From: Lionel Wolberger <lionel@userway.org>
- Date: Wed, 4 May 2022 20:08:26 +0300
- To: APA Chairs <group-apa-chairs@w3.org>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>, Michael Cooper <cooper@w3.org>
- Message-ID: <CAHOHNHfEAUC4Z5TVzS33gchDY36fUt9vbS_hrT7zcNZGiO-CHg@mail.gmail.com>
*All: Please comment if at all on the response below. I will then post this.* *Chairs/Michael: Please advise where I post this to i18n.* *APA comment regarding the i18n glossaryhttps://www.w3.org/TR/i18n-glossary/ <https://www.w3.org/TR/i18n-glossary/>* The APA wishes to bring to i18n's attention the lack of terms in this glossary relating to alternative reading experiences, particularly screen-reader, AAC symbol-based, and gesture- based communication experiences. We did expect to find definitions in the glossary, here is why. Before elaborating further, we assure you: APA does not ask i18n to define topics out of scope of i18n's publications. But that's the point. To understand the glossary's scope APA did a survey of documents produced by i18n, starting with those listed on https://www.w3.org/standards/webdesign/i18n. We find i18n addressing sight-based reading in general (.g., typography and graphemes) without many references if at all to aural-based reading (e.g. a screen reader experience), symbol-based reading (e.g. an AAC-reading based experience, such as that raised by i18n in issue 144 [ https://github.com/w3c/personalization-semantics/issues/144]) or sign language, although the international differences in sign language (e.g. ASL, BSL, CSL) are well known. To understand why these terms were not found, APA did a quick survey of documents produced by i18n, particularly those listed on its home page https://www.w3.org/standards/webdesign/i18n. We can understand that currently these other modes of communication may not be addressed, but we do expect them to be addressed in future, as APA is currently promoting specifications regarding such language experiences to CR status and publication. This work will give ample reason for i18n to refer to them. We would like to discuss this with i18n, and will reach out for a meeting at the upcoming TPAC. Lionel Wolberger COO, UserWay Inc. lionel@userway.org UserWay.org <http://userway.org/> <https://userway.org>[image: text]
Received on Wednesday, 4 May 2022 17:09:15 UTC