Wikipedia talk:Manual of Style/Accessibility/Data tables tutorial: Difference between revisions

Revision as of 21:58, 13 September 2010

Revision as of 22:42, 13 September 2010

Line 338:

:* "... if the TABLE element contains no COLGROUP or COL elements, user agents should base the number of columns on what is required by the rows. The number of columns is equal to the number of columns required by the row with the most columns, including cells that span multiple columns. For any row that has fewer than this number of columns, the end of that row should be padded with empty cells."

:So user agents should supply empty cells (rather than failing to provide anything). Agents that conform to h-11.2.4.3 will not cause any accessibility issues specific to disabled users; but may have accessibility implications for all users of text-only agents (since they generally do not distinguish between empty and row-spanned cells). --[[User:RexxS|RexxS]] ([[User talk:RexxS|talk]]) 21:58, 13 September 2010 (UTC)

== Avoiding rowspan/colspan ==

"Old screen readers and user agents that do not conform to UAAG do not handle rowspan / colspan efficiently. The result can be very confusing for users of these technologies." - this seems to imply that user agents that ''do'' conform to UAAG don't have problems with rowspan/colspan. Since I don't think any user agent fully conforms to UAAG, what are we saying? This opinion is reflected in Wikipedia already ([[Web Accessibility Initiative#User Agent Accessibility Guidelines (UAAG)]]). For example, I believe that Lynx conforms to UAAG as much as IE8 does, yet the rowspan vs empty cell problem demonstrably exists with Lynx. You may need to distinguish between graphical browsers and text-only browsers to give meaningful advice. --[[User:RexxS|RexxS]] ([[User talk:RexxS|talk]]) 22:42, 13 September 2010 (UTC)