Re: screen readers and punctuation

Hi there,
granted I missed the start of this thread.  yet it seems to illustrate 
what, speaking personally, seems to be a serious misunderstanding.  There 
are  many many different screen readers for various environments.  While I 
have certainly not tried them all, from my personal experience every one 
of them I have used since 1988  provided a way for me, as an individual 
user, to decide how much and how little punctuation I get at any given 
time.  Nothing you do  at your end  is going to uniformly impact  that, 
save for things like inflection, which too can be set...again with the 
several programs I have personally used.  In  some cases  even unique 
punctuation can be allowed, or restricted.  There are times when I tell my 
screen reader to say all punctuation...when I am playing hangman for 
example.  There are times when I desire very little, when reading dickens 
allowing inflection of the voice serving as my speech to do the work.  As 
I type  I get a different level, than if I am reading and so forth.
However, again speaking personally, nothing you do in your code is going 
to  change what I have told my screen reader to provide. it might motivate 
me to make adjustments, but this will not be a uniform experience for 
every screen reader user encountering your content.  These settings are 
individual in nature, as should be the case in my personal opinion.
Kare



On Thu, 14 Feb 2019, Mark Rogers wrote:

> Does wrapping numbers in an HTML <data> element affect how screen readers voice punctuation?
>
> For example:
> <data value="2345.00">$2,345.00</data>
>
> The data element seems like a useful hint that the contents aren't regular text, and punctuation may be important.
>
> Best Regards
> Mark
>
> -- 
> Mark Rogers - mark.rogers@powermapper.com
> PowerMapper Software Ltd - www.powermapper.com
> Registered in Scotland No 362274 Quartermile 2 Edinburgh EH3 9GL
>
>
>
> On 13/02/2019, 17:57, "Léonie Watson" <tink@tink.uk> wrote:
>
>    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
>
>
>
>