I just ran http://fae.cita.illinois.edu/ on /filter/tips and got the following errors:

The summary attribute value for each data table on a page should be unique.  
Warn: 2 data tables (out of 2 total) do not meet the criteria.
Each th element in a complex data table must have an id attribute whose value is unique relative to all ids on the page.
Fail: 3 th elements (out of 3 total in 1 complex data table) do not meet the criteria.
Each td element in a complex data table must have a headers attribute that references the id attributes of associated th elements.
Fail: 30 td elements (out of 30 total in 1 complex data table) do not meet the criteria.

Best practice is defined here - http://html.cita.illinois.edu/nav/dtable/
http://html.cita.illinois.edu/nav/dtable/

Comments

Jeff Burnz’s picture

Jeff Burnz commented

Subscribe

mgifford’s picture

mgifford
he/him
Primary language English
commented

A bit more on this from FAE:
http://html.cita.illinois.edu/nav/dtable/

And then updated for HTML5:
http://www.w3.org/TR/html5/attributes-common-to-td-and-th-elements.html#...

It's ultimately just about adding more semantics to tables by default. Filter tips are presently pretty public if you allow comments - http://openconcept.ca/filter/tips

It's ultimately a matter of setting an ID in the TH element and then pointing to it in the TD element as an attribute like headers="header1".

Fixing this in core will again propagate a best practice in D8.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Active » Postponed

Postponing this because ultimately the theme table needs to be able to support the scope and headers attributes.

http://tink.co.uk/2010/08/screen-reader-support-for-html-tables/
http://webaim.org/techniques/tables/data

mgifford’s picture

mgifford
he/him
Primary language English
commented

Just opened a new issue based on this tread - #1645308: Improve table semantics by adding scope or headers/id attributes to theme_table()

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: Compose tips tables need better use of id's & summary elements » Accessibility: Compose tips tables need better use of id's & summary elements
Issue summary: View changes
mgifford’s picture

mgifford
he/him
Primary language English
commented
Version: 8.0.x-dev » 8.1.x-dev

I don't think this would need to be postponed any more, but will probably need to get nudged back to 8.1.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Postponed » Active

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue tags: +wcag412

Tagging for https://www.w3.org/WAI/WCAG21/Understanding/name-role-value

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.