E-mail List Archives
Re: Forcing screen reader pronunciation ofabbreviation important to a brand
From: Jonathan Avila
Date: Apr 13, 2018 10:50AM
- Next message: Steve Green: "Styling of video captions"
- Previous message: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Next message in Thread: JP Jamous: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message in Thread: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- View all messages in this Thread
> 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.
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Duff Johnson
Sent: Friday, April 13, 2018 12:30 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Forcing screen reader pronunciation of abbreviation important to a brand
I thought you all were W3C people! ;-)
This was incorporated into PDF 2.0, which was published last year.
Pronunciation Lexicon Specification (PLS) Version 1.0, (October 2008), https://www.w3.org/TR/pronunciation-lexicon/
How (and whether) browsers understand this stuff for AT purposes is something I don't know...
Duff.
> On Apr 13, 2018, at 12:22, Jonathan Avila < <EMAIL REMOVED> > wrote:
>
> I would be careful about assuming that screen readers will announce aria-label on non-interactive elements. Also when you write out phonetically things it has a negative impact on braille. I blogged about this a few years ago.
> https://www.levelaccess.com/zip-z-p-z-p-forcing-correct-pronunciation-
> screen-readers/
>
> 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.
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> JP Jamous
> Sent: Friday, April 13, 2018 11:53 AM
> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Forcing screen reader pronunciation of
> abbreviation important to a brand
>
> You can accomplish this by various ways. It depends on the situation you have at hand. The bottom line is you use ARIA to hijack the HTML element. It may not be the best method from a semantic prospective, but it gets the job done.
>
> For example if I have a paragraph:
>
> <p>
> You have purchased NE1254 for $300.
> </p>
> You can hijack NE1254 using ARIA.
>
> <p>
> You have purchased
> <span aria-label=" N E 1254">
> NE1254</span>
> for $300.
> </p>
>
> I hope that helps.
>
> --------------------
> JP Jamous
> Senior Digital Accessibility Engineer
> E-Mail Me |Join My LinkedIn Network
> --------------------
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> JR Accessibility
> Sent: Friday, April 13, 2018 8:55 AM
> To: <EMAIL REMOVED>
> Subject: [WebAIM] Forcing screen reader pronunciation of abbreviation
> important to a brand
>
> Is it possible to force a screen reader to pronounce a two-letter abbreviation a certain way, rather than the way the screen reader software wants to pronounce it?
>
> In a previous WebAIM discussion from 2014, Geri Druckman suggested using the HTML <abbr> tag, but I cannot get that to work.
> https://webaim.org/discussion/mail_thread?threadb65
>
>
> For the sake of example suppose my company's name is Nova-Echo but we go by NE (which should be pronounced 'N E') in our product numbers and in our preferred customer program, MyNE (which should be pronounced 'My N E').
>
> The default pronunciation of the letters 'N' and 'E' next to each other in NVDA is 'northeast' and in JAWS it is 'knee'. This leads to undesirable pronunciations of our product numbers, such as 'northeast 1234' or 'knee 1234', and of our preferred customer program 'my northeast' or 'my knee'.
>
> How can we force the screen readers to pronounce these items the way we want them to?
>
>
> I have placed some sample HTML on my Google Drive, that contains
> additional
> examples:
> https://drive.google.com/file/d/1SiAN6ewa70q9L_SqmcxIwIuYQv_mEKRr/view
> ?usp=sharing
>
> Also a spreadsheet with the pronunciations I observed in NVDA and JAWS:
> https://drive.google.com/open?idC3RhocHOdtuGJ0uopLfQtGA4EF3pWEusM_A
> NYQB9Kc
>
> Thank you very much.
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
>
- Next message: Steve Green: "Styling of video captions"
- Previous message: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Next message in Thread: JP Jamous: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message in Thread: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- View all messages in this Thread