WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Forcing screen reader pronunciation ofabbreviation important to a brand

for

From: Jonathan Avila
Date: Apr 13, 2018 10:50AM

> How (and whether) browsers understand this stuff for AT purposes is something I don't know...

I haven't' looked at a demo page but I don't think this information is communicated through the accessibility API to screen readers and thus not passed to TTS engines. Internally in JAWS scripts there is some support to control the TTS using markup -- but as far as I know that is not controllable by content authors. So in practical reality if there is no accessibility support for something created 10 years ago I don't see it as a viable option. It might be helpful to know what user agents this specification has been implemented in such as voice assistants, etc.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
<EMAIL REMOVED>
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.