RE: WG discussion: Nov 5, 2013: role=group technique

So, if it is not identified as a table, give it is a layout table, which assumes no relationship of separated areas of the area is required, does this also effect reading order of information, and if so how is reading order ensured?


-----Original Message-----
From: Sailesh Panchang [mailto:spanchang02@yahoo.com] 
Sent: Monday, November 25, 2013 10:27 AM
To: BruceBailey
Cc: WCAG
Subject: RE: WG discussion: Nov 5, 2013: role=group technique

Hi Bruce,
Role=presentation on the table will  prevent the table being exposed as a table to AT. The contents of the table are still available to all. A screen reader user will not be tempted to navigate this content as a table if the role were not there.  
Rightho,
Sailesh



--------------------------------------------
On Mon, 11/25/13, Bailey, Bruce <Bailey@Access-Board.gov> wrote:

 Subject: RE: WG discussion: Nov 5, 2013: role=group technique
 To: "Sailesh Panchang" <spanchang02@yahoo.com>
 Cc: "WCAG" <w3c-wai-gl@w3.org>
 Date: Monday, November 25, 2013, 7:02 AM
 
 Thanks Sailesh.  I thought aria
 role=presentation causes AT to ignore the element.  So  would this not hide the table and the content therein?
 
 -----Original Message-----
 From: Sailesh Panchang [mailto:spanchang02@yahoo.com]
 
 Sent: Saturday, November 23, 2013 7:54 PM
 To: WCAG
 Cc: Bailey, Bruce
 Subject: Re: WG discussion: Nov 5, 2013: role=group  technique
 
 Bruce,
 With respect to your comment on use of role=presentation on  the table with credit cards in example#2:
 It is a layout table and role=presentation helps to remove  any ambiguity in its interpretation by AT.
 NVDA, for instance will expose it as a table in FF if the  role is absent.
 
 Regards,
 Sailesh

Received on Monday, 25 November 2013 15:35:17 UTC