RE: Action item: table with TH with and without scope

Hi Sailesh

I took the liberty of removing the ids since they are not needed for the
test, and there were some duplicates that were messing up the validator...
and I did a few other little clean things make it validate...
http://davidmacd.com/test/sailesh-table-test.html

========================
Test results
JAWS 14.0.6005  and IE 10.09 
First table validates h3 headings, and reads well..... the h3 did not hurt
or help the navigation using standard table navigation techniques. However
the h3 headings did allow pressing "h" to go from section to section of the
table, and a list of headings and proper navigation to them.

However it did allow pressing "h" to go from section to section of the
table, and a list of headings and proper navigation to them

Second table. Did not read well, in that, when I navigated into the a column
header all the other table headers to the left read
When I navigated into a row header the row headers above it read, which is
confusing an inaccurate.

================
JAWS  14.0.6005  Firefox 24
First table validates h3 headings, and reads well..... the h3 did not hurt
or help the navigation using standard table navigation techniques. However
the h3 headings did allow pressing "h" to go from section to section of the
table, and a list of headings and proper navigation to them.

Second table. Did not read well, when I navigated into the a column header
all the other table headers to the left read
When I navigated into a row header the row headers above it read, which is
confusing an inaccurate.

==============
aViewer examination of API reporting
---The h3s are reported to the accessibility API
- when a cell is selected the accParent includes all data in the <tr> which
is the parent
-- <td> cells did not report their related <th>
--<th>cells reported a accRole of column Header which may be enough to
inform AT
--- the scope does not appear to change what is reported to the API, but it
makes a big difference on how JAWS reads the table

I'm still not sure whether AT is crawling the DOM or the API to read the
related <th> levels, would need more testing for that...

I have to run and can't do NVDA and VoiceOver right now... others are free
to jump in...

Cheers,
David MacDonald

CanAdapt Solutions Inc.
Tel:  613.235.4902
http://ca.linkedin.com/in/davidmacdonald100
www.Can-Adapt.com
   
  Adapting the web to all users
            Including those with disabilities

This e-mail originates from CanAdapt Solutions Inc. Any distribution, use or
copying of this e-mail or the information it contains by other than the
intended recipient(s) is unauthorized. If you are not the intended
recipient, please notify me at the telephone number shown above or by return
e-mail and delete this communication and any copy immediately. Thank you.

Le présent courriel a été expédié par CanAdapt Solutions Inc. Toute
distribution, utilisation ou reproduction du courriel ou des renseignements
qui s'y trouvent par une personne autre que son destinataire prévu est
interdite. Si vous avez reçu le message par erreur, veuillez m'en aviser par
téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la
version originale de la communication ainsi que toutes ses copies. Je vous
remercie de votre collaboration.


-----Original Message-----
From: Sailesh Panchang [mailto:spanchang02@yahoo.com] 
Sent: October 17, 2013 11:21 PM
To: WCAG; Joshue O Connor
Subject: Action item: table with TH with and without scope

Survey items #9 and 11::
The comments in May 2013  were primarily influenced because of better
support for the scope attribute by JAWS and NVDA.
NVDA 2012 like JAWS read all cells marked up as TH to the left of current
cell (in column header rows) and all cells marked up as TH above current
cell for row header cells. (NVDA 2013 does not do so now) And I was using an
older version of FF in April / May.
Hence changes were suggested to H63 and H51 (survey items 9 and 11.
This comment was never submitted as a new technique but suggested a few
changes to the existing technique.
Representing it as a new technique in the survey is not appropriate. 
For H63 survey item#9: The example refers to a 'published schedule' but the
code that follows that is a contact info table.
That contact Info table is from a link of the Resources page for H63.
Here is a link to tables marked up with TH with and without the scope
attribute.
http://mars.dequecloud.com/demo/Table_scopeDemo.htm

Regards,
Sailesh

Received on Saturday, 19 October 2013 14:39:33 UTC