WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Readability of abreviated terms

for

From: Mallory
Date: Dec 11, 2019 3:43AM

I agree with your opinion, in general.

AT dictionaries tend to set how acronyms and abbreviations are pronounced; some users can change these, but I'm not certain if it's possible to change them in all text-to-speech softwares.

However: if it's an uncommon acronym or abbreviation, it's considered good practice to spell out the full words at least once, the first time the term is used. https://www.w3.org/WAI/WCAG21/Understanding/abbreviations.html

I would personally expect "QA" in a professional development, QA or general testing environment to not need this full spell out, however for audiences outside these areas (including managers/execs, content writers, or the general public), it would be good to say once "quality assurance (QA)"...

I would put anyone in training under the "general public" group. A screen reader user just getting started may potentially not run across "QA" as a term before (who knows) and so if there's any standard training docs given out to newbie hires, it would be good to spell out all acronyms and abbreviations at least once, to let these users match however their SR reads to what the term means.

cheers,
Mallory

On Wed, Dec 11, 2019, at 7:00 AM, Surendra Kumar wrote:
> Hi all,
>
>
>
> I hope everyone is having a good time.
>
>
>
> I've some doubts on how screen readers should pronounce certain abbreviated
> terms. For instance, if I write "QA" (Quality Assurance), it will be read as
> "Ka" instead of "Q A". Can we take it as an accessibility defect? In my
> opinion, we should not, because readability of such abbreviated terms may be
> TTS-dependent.
>
> > > > >