table accessibility Archives - The Accessibility Guy

Introduction

Hello, and welcome to the Accessibility Guy channel. Today we’re going to be looking all about table accessibility in Adobe Acrobat Pro. We will cover topics like using the reading order tool to tag individual cells, setting the scope of individual cells, fixing row and column-span problems, and adding associated header IDs for a header and data cell connection.

Utilizing the Reading Order Tool for Tagging Cells

To begin, launch the reading order tool by selecting the accessibility button and then choosing “Reading Order.” You may want to deselect “Show table cells” and “Show tables and figures” to make it easier to see the text. Select the text that should be together and click on “Text Paragraph” to group them. The checkboxes greatly change the view of the table:

Cleaning Up the Tags Panel

Make sure all cells are in the correct row by going through the tags, cutting and pasting them to the right location when needed. Set all cells in the first row as table data cells, and change any incorrectly labeled paragraph tags to table data cell tags. Properly format all table rows, ensuring that table header (TH) and table data (TD) cells contain the contents of the corresponding cell.

Setting the Scope of Table Headers

With the reading order tool open, right-click on the table and select “Table Editor.” Select all table header cells at the top of the table, right-click and select “Table Cell Properties,” and change the scope from none to “Column.” If you have table headers on the row side, you can set the scope to “Row” as needed.

Launch Reading order tool

Right-click inside of the table and select Table editor

Select the cells you want to set the scope for

Right-click and select table cell properties

Adjust the scope to either row, column, or both

Making a Data Connection Between Table Headers and Contents

Right-click in the table and select “Table Editor,” followed by “Auto Generate Header Cell IDs.” This will provide a name for each heading tag. For each group of table data cells, right-click and select “Table Cell Properties.” Add the corresponding header ID to the “Associated Header Cell IDs” section. This step is not required for all standards.

Conclusion

This comprehensive guide has demonstrated how to make tables accessible in Adobe Acrobat Pro using various tools, including the reading order tool, setting scope, and more. By following these best practices, you can ensure your tables are accessible to all users. Don’t forget to like and subscribe for more personalized tips and instructions on accessibility best practices.

Making tables accessible in Canvas can be easy if you set them up correctly! Using tables for layout purposes should be avoided. Use tables for displaying data only and use Headers and Scope. This is because assistive technology uses specialized controls when in a table.

Data tables should always include table headers (the <th> element). For short tables and for tables whose data are self-explanatory, column headers are sufficient. For long tables or tables where data may be confusing, it is best to include row and column headers. <th> elements should always have a scope attribute. Column headers should include scope=”col”, and row headers should include scope=”row”. Including scope attributes allow assistive technology to better understand the logical relationships presented in the table.

Use Table Captions

Tables can be given an accessible name with the <caption> element. Screen readers allow users to view a list of tables on the page. If the table has an accessible name, a screen reader will provide that name to the user. If not, the screen reader may only read the number of rows and columns. Thus, a <caption> provides substantial usability benefits, especially if there is more than one table on the page. <caption> elements are visible to sighted users as well.

Avoid Complex Tables

We recommend avoiding tables with multiple levels of row or column headers and headers that span multiple rows or columns. Such tables may be difficult to implement with the correct markup and scope attributes, and even if implemented correctly, may be difficult for users to understand. In most cases, some other presentation of the data, including presenting multiple tables, may be an equally effective alternative to a single, complex table.

Avoid Empty Cells for Formatting

Table authors may choose to use empty cells to visually format the table, such as to indicate a division in various sections of the table. While this practice may make sense for sighted users, it may not work for blind users. We recommend avoiding blank table cells, especially when those table cells are used for formatting.