Wikipedia:Manual of Style/Accessibility/Data tables tutorial

This is an old revision of this page, as edited by Dodoïste (talk | contribs) at 22:46, 29 August 2010. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Providing abbreviations for long headers

  • Priority: ... (... accessibility level)
  • Difficulty: ...

Voice browsers might read aloud this data table in the following order:[1]

Caption: [caption text]
[column header 1]: [row header 1], [column header 2]: [cell 1,2], [column header 3]: [cell 1,3]
[column header 1]: [row header 2], [column header 2]: [cell 2,2], [column header 3]: [cell 2,3]

...

Note that each column header is repeated when reading every row, so an abbreviation could be added to long headers using the abbr="..." attribute[2], for example:

{|
|+ [caption text]
|-
! scope="col" abbr="Wikipedian" | Wikipedia editor
! scope="col" abbr="Edits"      | Number of edits
! scope="col"                   | Last edit
! scope="col" abbr="Donations"  | Donations (US$)
|-
...

In this example all column headers have an abbreviation except the column with the date of the last edit, which is short enough.

Images and color

Images or colors inside a table should meet the requirements for images and color.

Images

  • Priority: ... (... accessibility level)
  • Difficulty: ...

Images used in tables are usually decorative icons so they need either:

  1. a minimal alt text (|alt= ...);
  2. to be unlinked and empty alt text (|link=|alt=).

For details and explanations concerning images that are not decorative, see WP:ALT.

Note that images in headers can by particularly annoying for screen reader users if they are badly handled. If the image doesn't comply to the criterions above, the filename will be part of the header title. The filename will be read aloud in every cell under the header containing the icon.

Color

  • Priority: high (A accessibility level)
  • Difficulty: ... (not yet rated)

Correct headers structure

  • Priority: high (A accessibility level)
  • Difficulty: ...

Several column headers placed inside the tables to separate visually the table, see the example on the best practices. Split the table in several tables.

Row header not relevant as a header (date is chosen instead of the album title), example

Couldn't think of a title

  • Priority: ... (... accessibility level)
  • Difficulty: ...


Bonus guidelines

Provide meaningful and precise headers title

  • Priority: bonus (this is not an accessibility criterion, but is an usability criterion)
  • Difficulty: ... (not yet rated)

Row or column headers should not use colspan/rowspan to span several rows or columns without providing sub-headers.

Row headers spanning several rows (without more precise sub row headers), example with an issue on the date

Avoiding more than two levels of headers

  • Priority: unknown (recommended by WebAIM techniques)
  • Difficulty: ...

Tables should not contain more than two levels of headers (which means 1) headers 2) sub-headers; but no 3) sub-sub headers)[3].

Avoiding rowspan/colpan

  • Priority: bonus (this criterion is not part of any accessibility referential and has limited impact)
  • Difficulty: very high (users like those attributes for presentation and are reluctant to remove them)

Couldn't think of a title

  • Priority: ... (... accessibility level)
  • Difficulty: ...

References