- From: Charles McCathieNevile <chaals@opera.com>
- Date: Fri, 14 Sep 2007 10:30:54 +0200
- To: "Phill Jenkins" <pjenkins@us.ibm.com>, w3c-wai-ig@w3.org
- Cc: support@gwmicro.com, "Christophe Strobbe" <christophe.strobbe@esat.kuleuven.ac.be>
On Thu, 13 Sep 2007 16:24:38 +0200, Phill Jenkins <pjenkins@us.ibm.com> wrote: > Instead of asking users, I believe you should be asking the screen reader > developers if or when they plan to support it. I think it is legitimate (and useful) to survey the current state of the art, and the different screen readers and systems are something that different users might have. When I get connected I'll check with Opera 9.5 alpha / VoiceOver, and Safari/VoiceOver. I don't have windows, so can't check the screenreaders on the 9.5 alpha for windows, but I can ask our testers, who collectively have 4 screen readers available... > User agents have a role in the total accessible solution equation too. Indeed. Voice-enabled opera could potentially do this with media-specific style, for example (I haven't checked the details...) cheers Chaals > JAWS user groups are listed at > http://www.freedomscientific.com/fs_products/JAWS_UserGroups.asp > I copied GW Micro's WindowEye support e-mail above. > > Regards, > Phill Jenkins > > > > Christophe Strobbe <christophe.strobbe@esat.kuleuven.be> > Sent by: w3c-wai-ig-request@w3.org > 09/13/2007 09:01 AM > > To > w3c-wai-ig@w3.org > cc > > Subject > support for sub and sup in screen readers and talking browsers > > > > > > > > Hi, > > I recently read in a report on accessibility of mathematics and > science that screen readers can't tell the difference between sub and > sup in HTML, so a<sup>n</sup> and a<sub>n</sub> are both rendered the > same on a Braille display, namely as "an". > > I would like to collect some more data on the support of sub and sup > by screen readers and talking browsers and I have put together a > small test page for this purpose: <http://tinyurl.com/2qll7h>. The > page contains five examples of superscript and subscript and a few > combinations of these. > > With Fire Vox, the code samples given above are read as an emphatic > "an". The output for the other expressions is also misleading. I > would appreciate it if users of screen readers and talking browsers > could tell me what their systems output for each of the five > examples. I will then add the test results to the test page. > > Best regards, > Christophe > > -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk chaals@opera.com http://snapshot.opera.com - Kestrel (9.5α1)
Received on Friday, 14 September 2007 08:31:49 UTC