Adobe 09972554AD01A12 Accessibility Guide - Page 24

Tables, TH and TD, Headers, Regularity, Summary

Get Adobe 09972554AD01A12 - Acrobat Pro - Mac PDF manuals and user guides View all Adobe 09972554AD01A12 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

Using the Acrobat XI Pro Accessibility Checker screen readers won't read the alternate text. If additional description is required for the object beyond what can be provided in alternative text, provide a on-page description or link to a description of the non-text object. Note: See the related WCAG section: 1.1.1 Non-text Content. (A) Tables Because table structure can be complex, it is best practice to check them for accessibility manually. Rows: This check indicates whether each TR in a table is a child of Table, THead, TBody, or TFoot. To fix this issue ensure that any TR tags are a child of a Table, THead, TBody, or TFoot tag. Note: Related WCAG section: 1.3.1 Info and Relationships. (Level A) TH and TD: This check indicates whether a proper table structure exists. TH and TD must be children of a TR element; if not this check fails. To fix this issue, ensure that TH or TD tags are place under a TR tag. Note: See related WCAG section: 1.3.1 Info and Relationships (Level A) Headers: For accessibility, it's necessary that all tables in the PDF have a header. To fix this issue, ensure that all tables contain table header cells. Note: See the related WCAG section: 1.3.1 Info and Relationships (Level A) Regularity: To be accessible, tables must contain the same number of columns in each row, and rows in each column. To fix this issue, ensure that each table row has the same number of columns or the ColSpan and RowSpan properties of a cell are set properly to account for all cells in a row. Note: See the related WCAG section: 1.3.1 Info and Relationships (Level A) Summary: Table summaries are optional unless the table data cannot be understood without it. Summaries can improve accessibility in complex data tables or when the way in which the data is read may be important. To fix this issue, provide a table summary for data tables where it is needed to make the data easier to understand, or to provide instructions on the data should be reviewed. Note: See the related WCAG section: 1.3.1 Info and Relationships. (Level A) Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
Using the Acrobat XI Pro Accessibility Checker
21
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
screen readers won’t read the alternate text. If additional description is required for the object
beyond what can be provided in alternative text, provide a on-page description or link to a
description of the non-text object.
Note:
See the related WCAG section: 1.1.1 Non-text Content. (A)
Tables
Because table structure can be complex, it is best practice to check them for accessibility
manually.
Rows:
°is check indicates whether each TR in a table is a child of Table, THead, TBody, or
TFoot.
To fix this issue ensure that any TR tags are a child of a Table, THead, TBody, or TFoot tag.
Note:
Related WCAG section: 1.3.1 Info and Relationships. (Level A)
TH and TD:
°is check indicates whether a proper table structure exists. TH and TD must be
children of a TR element; if not this check fails.
To fix this issue, ensure that TH or TD tags are place under a TR tag.
Note:
See related WCAG section: 1.3.1 Info and Relationships (Level A)
Headers:
For accessibility, it’s necessary that all tables in the PDF have a header.
To fix this issue, ensure that all tables contain table header cells.
Note:
See the related WCAG section: 1.3.1 Info and Relationships (Level A)
Regularity:
To be accessible, tables must contain the same number of columns in each row, and
rows in each column.
To fix this issue, ensure that each table row has the same number of columns or the ColSpan and
RowSpan properties of a cell are set properly to account for all cells in a row.
Note:
See the related WCAG section: 1.3.1 Info and Relationships (Level A)
Summary:
Table summaries are optional unless the table data cannot be understood without it.
Summaries can improve accessibility in complex data tables or when the way in which the data
is read may be important.
To fix this issue, provide a table summary for data tables where it is needed to make the data
easier to understand, or to provide instructions on the data should be reviewed.
Note:
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)