- From: Léonie Watson <tink@tink.uk>
- Date: Wed, 13 Feb 2019 17:52:40 +0000
- To: Michellanne Li <michellanne.li@gmail.com>, w3c-wai-ig@w3.org
This has some practical advice for writing content that works for screen readers: https://accessibility.blog.gov.uk/2017/02/08/advice-for-creating-content-that-works-well-with-screen-readers/ The short answer is that you can't write content that works with all screen readers, so it's better not to try. It's also worth mentioning that the Deque article misses an important point. When it says that screen readers do not announce certain symbols. that is usually only the case when reading content in chunks (like paragraphs or sentences). For example, a screen reader may not announce the dash in 5th - 10th May, when reading this sentence as a whole, but it will when reading the text in smaller chunks like one character at a time. What tends to happen, is that if a screen reader user senses something doesn't quite make sense as they read it, they'll tend to look a little more closely at it. That's when they find the dash. Where a screen reader doesn't speak an asterisk as a marker for a required field, that can be mitigated in different ways - like using the required attribute on the field in question. This is good practice in any case of course. Léonie. On 13/02/2019 15:39, Michellanne Li wrote: > Hello all, > > I just read this piece from Deque on how screen readers address > punctuation: Why Don’t Screen Readers Always Read What’s on the Screen? > Part 1: Punctuation and Typographic Symbols > <https://www.deque.com/blog/dont-screen-readers-read-whats-screen-part-1-punctuation-typographic-symbols/>. > > > Since it was written in 2014, I am wondering if screen reader technology > has since been updated to better read out important symbols. > > Thanks! > > Michellanne Li > (512) 718-2207 > http://www.michellanne.com -- @LeonieWatson Carpe diem
Received on Wednesday, 13 February 2019 17:53:08 UTC