search

jasonzhyan / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome
0 stars 0 forks source link

ChromeVox doesn't deal well with phrasing elements #51

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Open the following HTML file, and read it with ChromeVox:

<!DOCTYPE html>
<html>
<body>
  <p>Here is some <em>emphasized</em> <span>emphasized</span> text.</p>
  <p>This <span>span</span> has no style, but <i>this one</i> is <strong>in a different voice</strong>.</p>
  <p>Let's define 3 terms: <dfn>term 1</dfn>, <dfn>term 2</dfn>, and
  <dfn>term 3</dfn>.</p>
</body>
</html>

As far as I can hear, there's no difference between different phrasing 
elements, even though they have different meanings. It's especially strange 
that an unstyled <span> would have any effect on the reading.

The Text-to-Speech engine does especially badly at lists of terms, where each 
term is wrapped in a phrasing element. It tends to say "comma" and "period" 
instead of just reading the sentence.

What version of the product are you using? On what operating system?
ChromeVox 1.16.0; Mac OS 10.7.2

Original issue reported on code.google.com by jyass...@gmail.com on 30 Jan 2012 at 8:50