search

w3c / pronunciation

Pronunciation Task Force deliverables
https://www.w3.org/WAI/APA/task-forces/pronunciation/
Other
20 stars 12 forks source link

comments from the Cognitive and Learning Disabilities Accessibility Task Force (COGA) #84

Open lseeman opened 3 years ago

lseeman commented 3 years ago

Hi

The Cognitive and Learning Disabilities Accessibility Task Force (COGA) of APA and AG in the WAI would like t comment on the Pronunciation User Scenarios and specification. Our perspective is slightly different as some of our end user groups often can not figure out mispronunciations, as our impairments often impact phonological processing. Anyway , Thanks to EA Dafran and Abi James for the review.

Pronunciation User Scenarios: we would recommend that an additional scenario is added to cover the challenges with dates, number, time, Roman numerals, post/zip code and money being misread by text to speech. We addressed this in one of the design patterns in Content usable : 4.4.6 Use Clear, Unambiguous Formatting and Punctuation. (See https://www.w3.org/TR/coga-usable/#use-clear-unambiguous-formatting-and-punctuation-pattern.) We would recommend that this scenario is not focussed on education materials (as there is a maths education one all reader) but could be related to accessing financial or government services e.g. applying for a loan or completing a tax return.

Specification for Spoken Presentation In HTML:

The use of data-ssml-phoneme-ph did not include any examples. It was not clear if a developer would be able to write the phonemes and know they would be correctly pronounced. Adding examples that can be tested would be beneficial.

It was not clear from the document how the html attribute would interact with this specification alongside an individuals choice of voice or the voices available on the devices. For example, if the language of the page is set to en-gb but an individual is using a device where only an American voice is available then this effects how values of properties such as date or telephone are announced with the voice default taking precedent and often misreading (e.g. 4/3/21 is announced as 3rd April 2021 instead of 4th March 2021 as the author intended). For languages where text to speech may not be available then this is more important that the this mark-up can be used to override the voice defaults then it can allow the content creator to write in cultural and linguistic requirements that are not currently supported by voice engines.

lseeman commented 3 years ago

please send feedback to the coga list public-cognitive-a11y-tf@w3.org as we often dont see github alerts

AutoSponge commented 3 years ago

Thank you for the detailed notes. We will likely need to break this up into several issues.

The say-as feature provides a mechanism for many of the issues presented. The TF will add such examples to our documentation for clarity. Additionally, we can address COGA issues directly and mention the benefits for accessibility that this technology will provide.