E-mail List Archives
Re: Readability of abreviated terms
From: Swift, Daniel P.
Date: Dec 11, 2019 6:43AM
- Next message: Birkir R. Gunnarsson: "Re: Readability of abreviated terms"
- Previous message: Mark Magennis: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Readability of abreviated terms"
- Previous message in Thread: Maxability A11Y: "Re: Readability of abreviated terms"
- View all messages in this Thread
General thought, it's a shame that the "abbr" (abbreviation) tag doesn't have a phonetic attribute. How does the abbreviation tag work with screen readers with the title attribute (example: <abbr title="Quality Assurance">QA</abbr>)? Do both the 'title' and text get read or is it just one or the other? I'm assuming a mixed bag across software since the mileage for the title attribute varies...
Dan Swift
Senior Web Specialist
University Communications and Marketing
West Chester University
610.738.0589
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Surendra Kumar
Sent: Wednesday, December 11, 2019 1:01 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Readability of abreviated terms
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.
- Next message: Birkir R. Gunnarsson: "Re: Readability of abreviated terms"
- Previous message: Mark Magennis: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Readability of abreviated terms"
- Previous message in Thread: Maxability A11Y: "Re: Readability of abreviated terms"
- View all messages in this Thread