Re: [EXTERNAL] DRAFT: Vendor Letter

Hello all,

Janina and I chatted about your proposed letter to AT vendors (we looked at the version on the GitHub wiki [1]). Overall we think it's great, but in order to provide a little more context at the start, we swapped the first two paragraphs around. Given that edit, we also tweaked the subject, to keep it clear that it's a question for the reader. Please find a revised version below [in markdown format, to match the GitHub wiki version], for your consideration.

Please note: before this (or something like it) gets sent, we will need to consult the ARIA WG. We have a proposed approach for doing so, for you to consider on your TF call: we'd emphasise the established education use cases [maybe also doing the same in the vendor email], and to have Janina and I check with the ARIA WG chairs whether they feel that the ARIA proposal could be extended to cover those use cases. How does that sound?

I'm not sure if I'll be able to make Monday's call, but Janina expects to, as usual. It's great to see things reaching the stage of engaging with the community; looking forward to further developments!

best regards,

Matthew and Janina



Audience: AT vendors and developers
Subject: Seeking your input on Pronunciation in HTML

The W3C's [Pronunciation Task Force]( aims to give authors control over pronunciation in HTML. This innovation will benefit many technologies, including smart speakers, read-aloud tools, and assistive technology (AT).

We identified multiple possible solutions for improving pronunciation on the web. We would like your opinions about two strategies for choosing a preferred solution.

Smart speakers can harvest text and markup from the web and provide support for app developers to use [SSML]( Read-aloud tools may use the [Web Speech API]( for speech synthesis, and can utilize SSML in supported contexts.

When it comes to AT, we have two possible strategies:

1. AT will process pronunciation information from the accessibility tree (AxTree) provided by the browser. This should allow AT to implement enhanced pronunciation without significant changes to architecture. This approach requires work to map SSML-in-HTML to the AxTree and accessibility APIs.

2. AT will parse the SSML-based pronunciation information from the DOM, directly. This approach is currently possible without additional work by others to support it. This may require significant changes in AT architecture.

Please let us know which approach you prefer for your products and the users you serve. If you have any questions for our group, use our public email: [](

Matthew Tylee Atkinson (he/him) 
Principal Accessibility Engineer 
TPG Interactive 
A Vispero Company 
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. 
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful. 

On 13/02/2023, 15:57, "Janina Sajka" < <>> wrote:

CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.

Thanks, Sarah.

So, in addition to expanding this excellent list for any missing
contacts, we will need specific email addresses for each. Is that
something you can help with while I and Matthew put our heads together
on the message content itself?


Wood, Sarah G writes:
> Hi Everyone,
> Below is the draft list I have based on conversations during the ATIA conference earlier this year. There are additional vendors we are still adding to the list that I did not talk to at the conference. Based on the type of vendor we might want to customize the letter a bit and we can talk about that in the meeting. But I am fine with meeting or not meeting today.
> Company Name:
> American Printing House
> Avaz Inc
> Building Wings
> Center for Assistive Technology Training
> Cognixion
> Crick Software Inc.
> Dolphin Computer Access
> Forbes AAC
> Ghotit LTD
> MatchWare
> ObjectiveEd
> ReadSpeaker
> Scanmarker
> Scanning Pens Inc
> Sensory Guru Ltd
> Smartbox Assistive Technology
> Texthelp
> Vispero
> Voice Dream
> Continual Engine US LLC
> KiwiWrite Software,LLC
> Acapela Group
> SpeakUnique
> The Voice Keeper
> Glean
> Lingraphica
> Microsoft
> Thanks,
> Sarah
> Sarah G. Wood, PhD (she, her, hers)
> Accessibility Scientist
> Accessibility Standards and Inclusive Technology (ASIT)
> Educational Testing Service (ETS)
> +1 609-406-5908
> <>
> From: Ali, Irfan < <>>
> Date: Monday, February 13, 2023 at 6:13 AM
> To: Janina Sajka < <>>
> Cc: Spoken Pronunciation Task Force < <>>
> Subject: [EXTERNAL] DRAFT: Vendor Letter
> CAUTION: This email originated from outside of our organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> Dear Janina,
> We had a called last week and discussed the DRAFT letter to the AT Vendors<> <;;sdata=QLAZuleNOnDJQAXKuORQOFc4nNhQ%2F1G7Ta70Ifj%2B1%2BY%3D&amp;reserved=0&gt;>. It appears that everyone is satisfied with the message unless someone has any additional comment/concerns.
> Sarah Wood is putting a list of the AT vendors to send this letter. I believe this letter should go from the APA chair. Please let me know the next step.
> Sarah, did you get a chance to summarize a vendor list?
> Folks- I am sure if we need to have a call today because we do not have any specific agenda. Let me know your thoughts?
> Regards,
> ---------------------------------------------------------------------------------------------------
> Irfan Ali
> Digital Accessibility Product Manager- Global | BlackRock
> Phone: +1 609.282.4378 | Mobile: +1 609.255.9571
> [signature_4025036698]
> This message may contain information that is confidential or privileged. If you are not the intended recipient, please advise the sender immediately and delete this message. See<> <;;;sdata=SDzoYa6tQYwPQdMTUpUKPAAbecALfBYPl6wUuGWMkfs%3D&amp;reserved=0&gt;> for further information. Please refer to<> <;;;sdata=Jo7YW%2FIzREYNhqDqXhM9BhnmkPApFxCa9uCuXzQTTog%3D&amp;reserved=0&gt;> for more information about BlackRock’s Privacy Policy.
> For a list of BlackRock's office addresses worldwide, see<> <;;;sdata=cXJYCozQERF6vreK1lBQXtV9LqR3hTnygbA2MambSQ8%3D&amp;reserved=0&gt;>.
> © 2023 BlackRock, Inc. All rights reserved.
> ________________________________
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> Thank you for your compliance.
> ________________________________


Janina Sajka (she/her/hers)
Accessibility Consultant <>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures <>

Linux Foundation Fellow <>

Received on Friday, 17 February 2023 18:23:53 UTC