Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Test for WCAG failure F46: using th elements, caption elements, or non-empty summary attributes in layout tables #145

Open
3 tasks
hannolans opened this issue Feb 17, 2014 · 1 comment

Comments

@hannolans
Copy link
Contributor

http://www.w3.org/TR/WCAG20-TECHS/failures.html#F46

The objective of this technique is to describe a failure that occurs when a table used only for layout includes either th elements, a summary attribute, or a caption element. This is a failure because it uses structural (or semantic) markup only for presentation. The intent of the HTML and XHTML table elements is to present data.

Although not commonly used in a layout table, the following structural markup would also be failures of Success Criterion 1.3.1 if used in a layout table:

headers attributes

scope attributes 

Tests

Procedure

  1. Examine the source code of the HTML or XHTML document for the table element
  2. If the table is used only to visually lay out elements within the content
    • Check that the table does not contain any th elements.
    • Check that the table element does not contain a non-empty summary attribute.
    • Check that the table element does not contain a caption element.
@hannolans
Copy link
Contributor Author

Related: H39, H51, H73 AND H43 (#114)
Already in QUAIL:

  • tableLayoutDataShouldNotHaveTh
  • tableLayoutHasNoSummary
  • tableLayoutHasNoCaption

Not yet in QUAIL:

  • tableLayoutDataShouldNotHaveHeaders
  • tableLayoutDataShouldNotHaveScope

Enhancements:

  • tableLayoutDataShouldNotHaveTh currently has a testability of 0, should be 1
  • tableLayoutHasNoSummary currently has testability of 0.5, should be 1
  • tableLayoutHasNoCaption has testability of 1, that is correct
  • all tests should first run isDataTable, but that test is checking for Th (https://github.com/kevee/quail/wiki/Layout-versus-data-tables). The isDataTable-check should not rely on th, summary, caption, headers and scope.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants