Quote:
Originally Posted by ElMiko
The questions is does the use of those tags make it easier to figure it out...
|
I'm not implying you discriminating disabled people, sorry for my bad wording.
But that's exactly what I said in the second paragraph, as previously said by Turtle91, tts/read screen DOES read "quote" out loud every single time it encountering blockquote tag ( at least in default setting), so it's obvious that any normal intellectualled person will be annoyed by overdosed hints. It's simply not needed.
For more details, I think the situation listed down below does not need to be accessibility buffed. ( not every situation of course, just what I can think of now.)
1. When the phrase is famous that everyone knows who said it.
2. The phrase already deeply infused in the human culture/the listener's culture, it just doesn't matter who and when it was said.
3. When the text already says " XXX said...... ".
4. When someone is saying something with so much emotion/passion, adding "quote" kills the vibe and ruins the big moment.
5. Posters/flyers and such short content. If it's really ambiguous, I think you can add title or something to let tts identify it.
And I think you can add tags or attributes to let div content do accessibility things. You can always layer more general tags.