WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Forcing screen reader pronunciation ofabbreviation important to a brand

for

From: Duff Johnson
Date: Apr 13, 2018 12:00PM

> 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.

That's interesting. To get that far the spec is (I believe?) supposed to have at least a couple of implementations…?

> 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.

Well… if JAWS doesn't do it that's mostly a statement about JAWS… and the actual size of this marketplace, not (necessarily) the quality or utility of the spec… :-(

> It might be helpful to know what user agents this specification has been implemented in such as voice assistants, etc.

It would indeed!

Duff.