Recent searches
Search options
Be wary when adding additional context only for #screenReader users. An example:
Say you're working on an e-commerce site, and some products have two prices to show how great a sale discount is. The before and after is made visually apparent via some aspect of text formatting, and you want to make it explicit for screen reader users too.
The first step is to ask if this is necessary. If a user encounters two consecutive prices and one is lower than the other, they may intuitively understand what's going on without any explicit signposting, and can verify how much they're gonna pay during the checkout process. Only your users can provide this verdict.
If it's determined that some additional context is helpful, you could format it as something like: "Was $14.99, now $8.99" (optionally swapping the prices). It's short and punchy in braille and speech, perfectly descriptive of the situation at hand, and mirrors how it may be spoken out loud on an ad.
Resist the temptation to go further than this. You do not need to say "original price: $14.99, current sale price: $8.99". This is much longer and more verbose, while adding nothing. It also implies that you think screen reader users need to be told what a price is and explained the concept of a sale, even though you're not doing so for other audiences.
You also don't need to spell out the word "dollars", format the price in words, repeat the product name, and so on. If you find yourself with screen-reader-only text like: "The current price of 500 Grams of Premium Oolong Tea was fourteen dollars and ninety-nine cents, and is now on sale for eight dollars and ninety-nine cents", it has gone way too far.
In short: Set out to identify the problems that actually need solving, and only solve those problems.
@jscholes People over-explaining stuff to screen reader users is one of my pet peeves. “Should we write out this phone number as individual number words so that the screen reader does not announce it as a large number?” 
@yatil @jscholes Actually, just write it like the locality in question writes their telephone numbers, there's bound to be a dash in there somewhere. Synthesizers, and some screen readers, can cope with this. For example, I live in the US and use a synthesizer that speaks in an American accent. I can write the number 888-555-1234, or the sometimes used (888) 555-1234, and my screen reader clearly says eight eight eight, five five five, one two three four. It even has a specific type of intonation pause for reading phone numbers like that. Now granted this means it won't do well with something like UK numbers because the scheme is different. What I might recommend is separating the country code from the number with a space. Else the country code bleeds into the number and if it does activate number words, plus eighteen billion etc, that would be confusing.