Specify role="presentation" as the table attribute. This will ensure accessibility to work well for users.Hi guys,
"can someone please explain the motivation in moving towards TABLE layouts in 4.1 where previous ExtJS versions had clean DIV constructs?"
if this is true this could cause serious problems in supporting WCAG 2.0. One part of WCAG which is used to support accessibility is, states that the use of table elements should be used :
"to present tabular information in a way that preserves relationships within the information even when users cannot see the table or the presentation format is changed. Information is considered tabular when logical relationships among text, numbers, images, or other data exist in two dimensions (vertical and horizontal). These relationships are represented in columns and rows, and the columns and rows must be recognizable in order for the logical relationships to be perceived." see http://www.w3.org/TR/WCAG20-TECHS/H51.html
so when table elements are used instead of divs to make up widgets and stuff, this could cause screenreaders to read this layout stuff too.
On WCAG's site:
"Suppose that a Web page is laid out using a table with 9 columns and 22 rows. The screen reader speaks the content of the cell at Column 1, Row 1 followed by the cells in columns 2, 3, 4 and so on to column 9. However, if any cell contains a nested table, the screen reader will read the entire nested table before it reads the next cell in the original (outer) table. For example, if the cell at column 3, row 6 contains a table with 6 columns and 5 rows, all of those cells will be read before Column 4, Row 6 of the original (outer) table. As a result, the meaningful sequence conveyed through visual presentation may not be perceivable when the content is spoken by a screen reader." see http://www.w3.org/TR/WCAG20-TECHS/F49.html
can someone confirm if the use of table layouts interferes with the wcag rules?