When it comes to PDF accessibility, tables present a host of potential problems. In this article, we\u2019ll examine some of the more common uses of tables, the potential issues they can introduce and how to address those issues.<\/p>\n\n\n\n
This is the sixth in an eight-part article series.<\/p>\n\n\n\n
Document creators will often use the table functionality in whatever authoring program they\u2019re using to help layout the content on the page. This can be an easy way to make stuff all line up, have consistent spacing when formatting text, etc., into columns and more. Then, so that it doesn\u2019t look<\/em> like a table, they\u2019ll hide the cell borders. Unfortunately, this creates problems from an accessibility standpoint.<\/p>\n\n\n\n When a screen reader lands on a Table tag in the Tags tree, it will tell the user that there\u2019s a \u201ctable of X<\/strong> number of columns and Y<\/strong> number of rows.\u201d As it reads the table it tries to find column and\/or row headers and associate the data in the table to those headers.<\/p>\n\n\n\n Of course, when authors use tables just for formatting, none of that structural information is accurate. The solution here is pretty straightforward. Take the content out of the Table and tag it properly with Paragraph (or other) tags that are more semantically appropriate<\/em>. In other words, use the most accurate tag for the content. Fortunately, CommonLook PDF makes this process incredibly easy. All remediators have to do is select the Table tag and then open its context men (or navigate to the Operations tab in the toolbar) and choose \u201cLinearize table.\u201d There are even options to linearize horizontally or vertically to help make sure the reading order ends up correct. Of course, you\u2019ll still want to verify the reading order<\/a>, but that\u2019s relatively easy.<\/p>\n\n\n\n Linearizing a table used for formatting is pretty easy. However, people will sometimes use data tables because they\u2019re a great way to organize and present related information. Tables aren\u2019t bad as long as they\u2019re used, structured and tagged correctly. When teaching a class and looking at a table in a document, someone once asked me, \u201cHow do I know it\u2019s a table?\u201d Quite simply, if there are column and\/or row headers (along the top and down the left side of the table) and if those cells are directly related to all of the content straight below them (or to the right), then that\u2019s a data table. Of course, sometimes that\u2019s where the simplicity of tables ends. That being said, here are some things to consider when it comes to data table accessibility:<\/p>\n\n\n\n Another thing to consider when putting tables into your document or tagging them in the PDF, is whether or not you want to include captions (authors) or summaries (remediators). Summaries or captions can be very helpful, especially for people using assistive technology, because they tell people the general idea of what the table\u2019s about without requiring someone to listen to the whole table. So, what\u2019s the difference?<\/p>\n\n\n\n Table 1: Considerations for Authors and PDF Remediators when working with Tables.<\/p>\n\n\n\n Here\u2019s another brief table to help illustrate (notice the caption above the table!):<\/p>\n\n\n\n Table 2: Comparison of Table Captions and Table Summaries<\/p>\n\n\n\n While both of the tables that I included in this article today have captions, something to consider, while designing your document, is that if the table is sufficiently described in the text of the document, you may not need to include a caption or a summary. When it comes to PDF remediation, there are checkpoints concerned with captions and summaries but, in reality, neither are required<\/em> to be compliant with accessibility standards. That said, using captions or summaries can make for a much better end-user experience.<\/p>\n\n\n\n Tables in documents can present some real accessibility issues in PDFs. If you\u2019re an author putting a table into your document\u2014make sure it\u2019s constructed well and it\u2019s not too complex. Also, verify that the content belongs<\/em> inside a table. If you\u2019re remediating a PDF, make sure to linearize tables that are just used for formatting and, if it\u2019s really a data table, make sure that <TH> cells are marked correctly, including with the proper scope. Link the data cells to the header cells as needed. And remember that CommonLook PDF makes this all a whole lot easier!<\/p>\n","protected":false},"excerpt":{"rendered":" When it comes to PDF accessibility, tables present a host of potential problems. In this article, we\u2019ll examine some of the more common uses of tables, the potential issues they […]<\/p>\n","protected":false},"author":12,"featured_media":86309,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14],"tags":[],"class_list":["post-86252","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tData Tables<\/h3>\n\n\n\n
Captions and Summaries<\/h2>\n\n\n\n
Authors<\/th> PDF Remediators<\/th><\/tr><\/thead> Use as simple a design as possible. If you\u2019ve got too many rows of column headers and especially if you\u2019ve got lots of row headers, that table can be hard for anyone to decipher \u2013 whether or not they\u2019re using assistive technology<\/td> Make sure that the header cells are tagged as <TH> (Table Header).<\/td><\/tr> In MS Word and PowerPoint, it\u2019s not possible to assign the scope to header cells. It\u2019s actually also not possible to make cells row headers. However, if you\u2019re using\u00a0CommonLook Office<\/a>\u00a0this can be done properly!<\/td> Make sure that the <TH> cells have the proper scope set \u2013Column<\/strong> or Row<\/strong> \u2013 depending on whether they\u2019re related to the data below them (column headers) or the data to the right (row headers).<\/td><\/tr> Don\u2019t allow single rows in your table to span over page breaks.<\/td> If rows (or whole tables) are split by a page break, make sure to merge them so that they\u2019re read logically.<\/td><\/tr> If your table is on multiple pages, make sure that the column headers repeat on each page (so people don\u2019t have to remember what the column headers are when they get to page 2).<\/td> If the table spans multiple pages in the PDF, artifact (untag) the column headers on the second (and subsequent) pages. Assistive technologies will use the column headers from the top of the table if they\u2019re tagged correctly.<\/td><\/tr> Show the lines! For people who are looking at the table, especially for people with dyslexia for example, the lines can make it much easier to \u201ctrack\u201d across rows and down columns.<\/td> Untag (artifact) the lines.<\/td><\/tr> Organize your information in a logical manner. Once your table is \u201cbuilt,\u201d place the cursor in the top left cell and then press the Tab key on your keyboard to navigate through the table. If the tabbing order makes sense, that\u2019s good. If it doesn\u2019t, change your table\u2019s layout!<\/td> In complex tables, you\u2019ll also need to give the header cells IDs and then link the data cells to the proper headers. That\u2019s a fairly complex process and, in fact, we could teach an entire class on tagging complex tables. However, CommonLook PDF makes this process incredibly easy. Once the column and row headers are properly tagged, the linking is done automatically with the click of a button.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n <\/th> Caption<\/th> Summary<\/th><\/tr><\/thead> Provides a synopsis of what\u2019s in the table?<\/th> Yes<\/td> Yes<\/td><\/tr> Shown visually on the page?<\/th> Yes<\/td> No<\/td><\/tr> Read by assistive technology?<\/th> Yes<\/td> Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Conclusion<\/h2>\n\n\n\n