- From: Phill Jenkins <pjenkins@us.ibm.com>
- Date: Thu, 13 Sep 2007 09:24:38 -0500
- To: w3c-wai-ig@w3.org
- Cc: support@gwmicro.com
- Message-ID: <OF900681A5.E45072A7-ON86257355.004F1082-86257355.004F3821@us.ibm.com>
Instead of asking users, I believe you should be asking the screen reader developers if or when they plan to support it. User agents have a role in the total accessible solution equation too. 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 -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Received on Thursday, 13 September 2007 14:24:49 UTC