[Blindmath] Another test of matrix accessibility

[Rasmussen, Lloyd]

I haven't looked at the examples.  And I don't know what configuration options JAWS or NVDA may have.  But Window-Eyes has a large number of options regarding how tables are presented to the user.  The most important one, for the earlier examples, is the Smart Table feature, which attempts to determine which tables are being used for layout and which for data.  The Smart Tables mode is on by default.  It tends to hide the fact that some cells have small sub-tables within them, or that the entire document is a large table.  You really can't control how the users will configure their screen readers, but might somewhere give people a hint as to what to expect.  

Students using assistive technology of any kind have to be savvy enough to use its features while they learn the course material.  I also thank you for the work you are doing and the example you are setting.  

>From another EE, BS Iowa State, 1969.

Lloyd Rasmussen, Senior Project Engineer
National Library Service for the Blind and Physically Handicapped
Library of Congress   202-707-0535
http://www.loc.gov/nls
The preceding opinions are my own and do not necessarily reflect those of the Library of Congress, NLS.



-----Original Message-----
From: blindmath-bounces at nfbnet.org [mailto:blindmath-bounces at nfbnet.org] On Behalf Of Steve Jacobson
Sent: Tuesday, November 22, 2011 10:24 AM
To: Blind Math list for those interested in mathematics
Subject: Re: [Blindmath] Another test of matrix accessibility

With Window-Eyes, all three examples were identified as tables and could be navigated cell by cell using table navigation keys.  Michael, does voiceOver not recognize the first example as a table?

One small thing I noticed that is simply a difference and not good or bad is that in the third example the word "Matrix" 
is in the table but doesn't show up as a separate row.  It is not visible as a row when using the table navigation keys but does show up if browsing the table without table cell navigation keys.  I suspect that this situation is probably handled differently by different screen readers, though, and don't think this would be a reason not to use the third approach.

Dick, thanks for taking the time you are taking with all of this, your work is really appreciated.

Best regards,

Steve Jacobson

On Tue, 22 Nov 2011 15:04:45 +0000, Michael Whapples wrote:

>I would possibly say both the second and third are better with 
>VoiceOver. It identifies each element as being in a
separate cell (I assume that is what you would want to be found). The first one its a single cell for the whole row (one cell per line).

>Michael Whapples
>On 22 Nov 2011, at 14:38, Richard Baldwin wrote:

>> I have attached a zip file containing an html file containing three 
>> possible candidates for use as matrix containers.
>> 
>> The first one is the apparent winner from the previous set of tests.
>> 
>> The other two are refinements of the first one that produce a more 
>> visually pleasing matrix. I would prefer to use one of the latter two 
>> provided that the improvement in visual appeal doesn't result in a loss of accessibility.
>> 
>> I would appreciate comments on the accessibility of the three using 
>> as many popular screen readers as possible.
>> 
>> Thanks,
>> Dick Baldwin
>> 
>> --
>> Richard G. Baldwin (Dick Baldwin)
>> Home of Baldwin's on-line Java Tutorials http://www.DickBaldwin.com
>> 
>> Professor of Computer Information Technology Austin Community College
>> (512) 223-4758
>> mailto:Baldwin at DickBaldwin.com
>> http://www.austincc.edu/baldwin/
>> <MatrixTest02.zip>

_______________________________________________